SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Command-line interface</title>

</head>

Command-line interface

</h1>

</header>

A command-line interface (CLI), sometimes called a command-line shell,<a href="#cite_note-1">[1]</a><a href="#cite_note-2">[2]</a> is a means of interacting with <a href="Software" title="Software">software</a> via <a href="Command_(computing)" title="Command (computing)">commands</a> – each formatted as a line of text. Command-line interfaces emerged in the mid-1960s, on <a href="Computer_terminal" title="Computer terminal">computer terminals</a>, as an interactive and more user-friendly alternative to the non-interactive mode available with <a href="Punched_cards" class="mw-redirect" title="Punched cards">punched cards</a>.<a href="#cite_note-3">[3]</a>

For nearly three decades, a CLI was the most common interface for software, but today a <a href="Graphical_user_interface" title="Graphical user interface">graphical user interface</a> (GUI) is more common. Nonetheless, many programs such as <a href="Operating_system" title="Operating system">operating system</a> and <a href="Software_development" title="Software development">software development</a> <a href="Utility_software" title="Utility software">utilities</a> still provide CLI.

A CLI enables <a href="Automation" title="Automation">automating</a> <a href="Computer_program" title="Computer program">programs</a> since commands can be stored in a <a href="Scripting_language" title="Scripting language">script</a> <a href="Computer_file" title="Computer file">file</a> that can be used repeatedly. A script allows its contained commands to be executed as group; as a program; as a command.

A CLI is made possible by command-line interpreters or command-line processors, which are programs that execute input commands.

Alternatives to a CLI include a GUI (including the <a href="Desktop_metaphor" title="Desktop metaphor">desktop metaphor</a> such as <a href="Windows" class="mw-redirect" title="Windows">Windows</a>), <a href="Text-based_user_interface" title="Text-based user interface">text-based</a> <a href="Menu_(computing)" title="Menu (computing)">menuing</a> (including <a href="DOS_Shell" title="DOS Shell">DOS Shell</a> and <a href="IBM_AIX_SMIT" class="mw-redirect" title="IBM AIX SMIT">IBM AIX SMIT</a>), and <a href="Keyboard_shortcut" title="Keyboard shortcut">keyboard shortcuts</a>.

<div class="mw-heading mw-heading2"><h2 id="Comparison_to_graphical_user_interfaces">Comparison to graphical user interfaces</h2></div>

Compared with a graphical user interface, a command-line interface requires fewer system resources to implement. Since options to commands are given in a few characters in each command line, an experienced user often finds the options easier to access. Automation of repetitive tasks is simplified by line editing and history mechanisms for storing frequently used sequences; this may extend to a <a href="Scripting_language" title="Scripting language">scripting language</a> that can take parameters and variable options. A command-line history can be kept, allowing review or repetition of commands.

A command-line system may require paper or online manuals for the user's reference, although often a help option provides a concise review of the options of a command. The command-line environment may not provide graphical enhancements such as different <a href="Computer_font" title="Computer font">fonts</a> or extended <a href="Window_(computing)" title="Window (computing)">edit windows</a> found in a GUI. It may be difficult for a new user to become familiar with all the commands and options available, compared with the <a href="Icon_(computing)" title="Icon (computing)">icons</a> and <a href="Drop-down_menu" class="mw-redirect" title="Drop-down menu">drop-down menus</a> of a graphical user interface, without reference to manuals.

<div class="mw-heading mw-heading2"><h2 id="Types">Types</h2></div>

<div class="mw-heading mw-heading3"><h3 id="Operating_system_command-line_interfaces">Operating system command-line interfaces</h3></div>

Operating system (OS) command-line interfaces are usually distinct programs supplied with the operating system. A program that implements such a text interface is often called a command-line interpreter, command processor or <a href="Shell_(computing)" title="Shell (computing)">shell</a>.

Examples of command-line interpreters include Nushell, <a href="Digital_Equipment_Corporation" title="Digital Equipment Corporation">DEC's</a> <a href="DIGITAL_Command_Language" title="DIGITAL Command Language">DIGITAL Command Language</a> (DCL) in <a href="OpenVMS" title="OpenVMS">OpenVMS</a> and <a href="RSX-11" title="RSX-11">RSX-11</a>, the various <a href="Unix_shell" title="Unix shell">Unix shells</a> (<a href="Bourne_shell" title="Bourne shell">sh</a>, <a href="KornShell" title="KornShell">ksh</a>, <a href="C_shell" title="C shell">csh</a>, <a href="Tcsh" title="Tcsh">tcsh</a>, <a href="Zsh" class="mw-redirect" title="Zsh">zsh</a>, <a href="Bash_(Unix_shell)" title="Bash (Unix shell)">Bash</a>, etc.), <a href="CP/M" title="CP/M">CP/M</a>'s <a href="Console_Command_Processor" class="mw-redirect" title="Console Command Processor">CCP</a>, <a href="DOS" title="DOS">DOS</a>' <a href="COMMAND.COM" title="COMMAND.COM">COMMAND.COM</a>, as well as the <a href="OS/2" title="OS/2">OS/2</a> and the Windows <a href="CMD.EXE" class="mw-redirect" title="CMD.EXE">CMD.EXE</a> programs, the latter groups being based heavily on DEC's RSX-11 and <a href="RSTS/E" title="RSTS/E">RSTS</a> CLIs. Under most operating systems, it is possible to replace the default shell program with alternatives; examples include <a href="4DOS" title="4DOS">4DOS</a> for DOS, <a href="4OS2" title="4OS2">4OS2</a> for OS/2, and <a href="Take_Command_Console" title="Take Command Console">4NT / Take Command</a> for Windows.

Although the term shell is often used to describe a command-line interpreter, strictly speaking, a <a href="Shell_(computing)" title="Shell (computing)">shell</a> is a command interpreter and processor and by extension a program that provides an interface (either a user interface (command-line interface, GUI, etc...) or a programming interface) to a command interpreter and processor and to the broad capabilities of the operating system. For example, the default Windows GUI is a shell GUI named <a href="EXPLORER.EXE" class="mw-redirect" title="EXPLORER.EXE">EXPLORER.EXE</a>, as defined in the SHELL=EXPLORER.EXE line in the WIN.INI configuration file. This program strictly speaking is a shell GUI and by extension a shell (strictly speaking the Windows shell is shell32.dll not explorer.exe which is a shell GUI for shell32.dll), but it is not a CLI (command-line interpreter) nor a shell CLI (shell command-line interface).

<div class="mw-heading mw-heading3"><h3 id="Application_command-line_interfaces">Application command-line interfaces</h3></div>

Application programs (as opposed to operating systems) may also have command-line interfaces.

An application program may support none, any, or all of these three major types of command-line interface mechanisms:

<ul><li>Parameters: Most command-line interfaces support a means to pass additional information to a program when it is launched.</li>

<li>Interactive command-line sessions: After launch, a program may provide an operator with an independent means to enter commands.</li>

<li>Inter-process communication: Most operating systems support means of <a href="Inter-process_communication" title="Inter-process communication">inter-process communication</a> (for example, <a href="Standard_streams" title="Standard streams">standard streams</a> or <a href="Named_pipe" title="Named pipe">named pipes</a>). Command lines from client processes may be redirected to a CLI program by one of these methods.</li></ul>

Some applications support a CLI, presenting their own prompt to the user and accepting command lines. Other programs support both a CLI and a GUI. In some cases, a GUI is simply a <a href="Wrapper_function" title="Wrapper function">wrapper</a> around a separate CLI <a href="Executable_file" class="mw-redirect" title="Executable file">executable file</a>. In other cases, a program may provide a CLI as an optional alternative to its GUI. CLIs and GUIs often support different functionality. For example, all features of <a href="MATLAB" title="MATLAB">MATLAB</a>, a <a href="Numerical_analysis" title="Numerical analysis">numerical analysis</a> computer program, are available via the CLI, whereas the MATLAB GUI exposes only a subset of features.

In <a href="Colossal_Cave_Adventure" title="Colossal Cave Adventure">Colossal Cave Adventure</a> from 1975, the user uses a CLI to enter one or two words to explore a cave system.

<div class="mw-heading mw-heading2"><h2 id="History">History</h2></div>

The command-line interface evolved from a form of communication conducted by people over <a href="Teleprinter" title="Teleprinter">teleprinter</a> (TTY) machines. Sometimes these involved sending an order or a confirmation using <a href="Telex" title="Telex">telex</a>. Early computer systems often used teleprinter as the means of interaction with an operator.

The mechanical teleprinter was replaced by a <a href="Dumb_terminal" class="mw-redirect" title="Dumb terminal">"glass tty"</a>, a keyboard and screen emulating the teleprinter. <a href="Computer_terminal#.22Intelligent.22_terminals" title="Computer terminal">"Smart" terminals</a> permitted additional functions, such as cursor movement over the entire screen, or local editing of data on the terminal for transmission to the computer. As the <a href="Microcomputer_revolution" class="mw-redirect" title="Microcomputer revolution">microcomputer revolution</a> replaced the traditional – minicomputer + terminals – <a href="Time_sharing" class="mw-redirect" title="Time sharing">time sharing</a> architecture, hardware terminals were replaced by <a href="Terminal_emulator" title="Terminal emulator">terminal emulators</a> — PC software that interpreted terminal signals sent through the PC's <a href="Serial_port" title="Serial port">serial ports</a>. These were typically used to interface an organization's new PC's with their existing mini- or mainframe computers, or to connect PC to PC. Some of these PCs were running <a href="Bulletin_Board_System" class="mw-redirect" title="Bulletin Board System">Bulletin Board System</a> software.

Early operating system CLIs were implemented as part of <a href="Resident_monitor" title="Resident monitor">resident monitor</a> programs, and could not easily be replaced. The first implementation of the shell as a replaceable component was part of the <a href="Multics" title="Multics">Multics</a> <a href="Time-sharing" title="Time-sharing">time-sharing</a> <a href="Operating_system" title="Operating system">operating system</a>.<a href="#cite_note-Unix_Shells-4">[4]</a> In 1964, <a href="MIT_Computation_Center" title="MIT Computation Center">MIT Computation Center</a> staff member <a href="Louis_Pouzin" title="Louis Pouzin">Louis Pouzin</a> developed the <a href="RUNCOM" title="RUNCOM">RUNCOM</a> tool for executing command scripts while allowing argument substitution.<a href="#cite_note-multicians-5">[5]</a> Pouzin coined the term <a href="Shell_(computing)" title="Shell (computing)">shell</a> to describe the technique of using commands like a programming language, and wrote a paper about how to implement the idea in the <a href="Multics" title="Multics">Multics</a> operating system.<a href="#cite_note-Metz_2013-6">[6]</a> Pouzin returned to his native France in 1965, and the first Multics shell was developed by <a href="Glenda_Schroeder" title="Glenda Schroeder">Glenda Schroeder</a>.<a href="#cite_note-multicians-5">[5]</a>

The first <a href="Unix_shell" title="Unix shell">Unix shell</a>, the <a href="Thompson_shell" title="Thompson shell">V6 shell</a>, was developed by <a href="Ken_Thompson" title="Ken Thompson">Ken Thompson</a> in 1971 at <a href="Bell_Labs" title="Bell Labs">Bell Labs</a> and was modeled after Schroeder's Multics shell.<a href="#cite_note-Mazieres_2004-7">[7]</a><a href="#cite_note-ibm-8">[8]</a> The <a href="Bourne_shell" title="Bourne shell">Bourne shell</a> was introduced in 1977 as a replacement for the V6 shell. Although it is used as an interactive command interpreter, it was also intended as a scripting language and contains most of the features that are commonly considered to produce structured programs. The Bourne shell led to the development of the <a href="KornShell" title="KornShell">KornShell</a> (ksh), <a href="Almquist_shell" title="Almquist shell">Almquist shell</a> (ash), and the popular <a href="Bourne-again_shell" class="mw-redirect" title="Bourne-again shell">Bourne-again shell</a> (or Bash).<a href="#cite_note-ibm-8">[8]</a>

Early microcomputers themselves were based on a command-line interface such as <a href="CP/M" title="CP/M">CP/M</a>, <a href="DOS" title="DOS">DOS</a> or <a href="AppleSoft_BASIC" class="mw-redirect" title="AppleSoft BASIC">AppleSoft BASIC</a>. During the 1980s and 1990s, the introduction of the <a href="Apple_Macintosh" class="mw-redirect" title="Apple Macintosh">Apple Macintosh</a> and of <a href="Microsoft_Windows" title="Microsoft Windows">Microsoft Windows</a> on PCs saw the command line interface as the primary user interface replaced by the <a href="Graphical_User_Interface" class="mw-redirect" title="Graphical User Interface">Graphical User Interface</a>.<a href="#cite_note-9">[9]</a> The command line remained available as an alternative user interface, often used by <a href="System_administrator" title="System administrator">system administrators</a> and other advanced users for system administration, <a href="Computer_programming" title="Computer programming">computer programming</a> and <a href="Batch_processing" title="Batch processing">batch processing</a>.

In November 2006, <a href="Microsoft" title="Microsoft">Microsoft</a> released version 1.0 of <a href="Windows_PowerShell" class="mw-redirect" title="Windows PowerShell">Windows PowerShell</a> (formerly codenamed Monad), which combined features of traditional Unix shells with their proprietary object-oriented <a href=".NET_Framework" title=".NET Framework">.NET Framework</a>. <a href="MinGW" title="MinGW">MinGW</a> and <a href="Cygwin" title="Cygwin">Cygwin</a> are <a href="Open-source_software" title="Open-source software">open-source</a> packages for Windows that offer a Unix-like CLI. Microsoft provides <a href="MKS_Inc." title="MKS Inc.">MKS Inc.</a>'s <a href="KornShell" title="KornShell">ksh</a> implementation MKS Korn shell for Windows through their <a href="Services_for_UNIX" class="mw-redirect" title="Services for UNIX">Services for UNIX</a> add-on.

Since 2001, the <a href="Macintosh" class="mw-redirect" title="Macintosh">Macintosh</a> operating system <a href="MacOS" title="MacOS">macOS</a> has been based on a <a href="Unix-like" title="Unix-like">Unix-like</a> operating system called <a href="Darwin_(operating_system)" title="Darwin (operating system)">Darwin</a>.<a href="#cite_note-10">[10]</a> On these computers, users can access a Unix-like command-line interface by running the <a href="Terminal_emulator" title="Terminal emulator">terminal emulator</a> program called <a href="Terminal_(macOS)" title="Terminal (macOS)">Terminal</a>, which is found in the Utilities sub-folder of the Applications folder, or by remotely logging into the machine using <a href="Ssh" class="mw-redirect" title="Ssh">ssh</a>. <a href="Z_shell" title="Z shell">Z shell</a> is the default shell for macOS; Bash, <a href="Tcsh" title="Tcsh">tcsh</a>, and the <a href="KornShell" title="KornShell">KornShell</a> are also provided. Before <a href="MacOS_Catalina" title="MacOS Catalina">macOS Catalina</a>, Bash was the default.

<div class="mw-heading mw-heading2"><h2 id="Usage">Usage</h2></div>

A CLI is used whenever a large vocabulary of commands or queries, coupled with a wide (or arbitrary) range of options, can be entered more rapidly as text than with a pure GUI. This is typically the case with <a href="Operating_system_shell" class="mw-redirect" title="Operating system shell">operating system command shells</a>. CLIs are also used by systems with insufficient resources to support a graphical user interface. Some computer language systems (such as <a href="Python_(programming_language)" title="Python (programming language)">Python</a>,<a href="#cite_note-11">[11]</a> <a href="Forth_(programming_language)" title="Forth (programming language)">Forth</a>, <a href="LISP" class="mw-redirect" title="LISP">LISP</a>, <a href="Rexx" title="Rexx">Rexx</a>, and many dialects of <a href="BASIC" title="BASIC">BASIC</a>) provide an interactive command-line mode to allow for rapid evaluation of code.

CLIs are often used by programmers and system administrators, in engineering and scientific environments, and by technically advanced personal computer users.<a href="#cite_note-12">[12]</a> CLIs are also popular among people with visual disabilities since the commands and responses can be displayed using <a href="Refreshable_Braille_display" class="mw-redirect" title="Refreshable Braille display">refreshable Braille displays</a>.

<div class="mw-heading mw-heading2"><h2 id="Anatomy_of_a_shell_CLI">Anatomy of a shell CLI</h2></div>

The general pattern of a command line is:<a href="#cite_note-Bash-13">[13]</a><a href="#cite_note-Microsoft_Windows-14">[14]</a>

<pre>prompt command param1 param2 param3 … paramN

</pre>

<ul><li><a href="#Command_prompt">prompt</a> — output by the program to indicate that its ready for input; a prompt may include contextual information and often ends with a symbol that provides a visual cue that input is expected</li>

<li>command — input by the user, a command is usually one of two classes:

<ol><li>Internal commands are recognized and processed by the command line interpreter. Internal commands are also called built-in commands.<a href="#cite_note-15">[15]</a></li>

<li>External commands run executables found in separate executable files. The command line interpreter searches for executable files with names matching the external command.<a href="#cite_note-16">[16]</a><a href="#cite_note-17">[17]</a></li></ol></li>

<li>param1 …paramN — parameters provided by the user. The format and meaning of the parameters depends upon the command. In the case of external commands, the values of the parameters are delivered to the program as it is launched by the OS. Parameters may be either <a href="#Arguments">arguments</a> or <a href="#Command-line_option">options</a>.</li></ul>

In this format, the delimiters between command-line elements are <a href="Whitespace_character" title="Whitespace character">whitespace characters</a> and the end-of-line delimiter is the <a href="Newline" title="Newline">newline</a> delimiter. This is a widely used (but not universal) convention.

A CLI can generally be considered as consisting of <a href="Syntax_(programming_languages)" title="Syntax (programming languages)">syntax</a> and <a href="Semantics" title="Semantics">semantics</a>. The syntax is the grammar that all commands must follow. In the case of <a href="Operating_system" title="Operating system">operating systems</a>, <a href="DOS" title="DOS">DOS</a> and <a href="Unix" title="Unix">Unix</a> each define their own set of rules that all commands must follow. In the case of <a href="Embedded_systems" class="mw-redirect" title="Embedded systems">embedded systems</a>, each vendor, such as <a href="Nortel" title="Nortel">Nortel</a>, <a href="Juniper_Networks" title="Juniper Networks">Juniper Networks</a> or <a href="Cisco_Systems" class="mw-redirect" title="Cisco Systems">Cisco Systems</a>, defines their own proprietary set of rules. These rules also dictate how a user navigates through the system of commands. The semantics define what sort of operations are possible, on what sort of data these operations can be performed, and how the grammar represents these operations and data—the symbolic meaning in the syntax.

Two different CLIs may agree on either syntax or semantics, but it is only when they agree on both that they can be considered sufficiently similar to allow users to use both CLIs without needing to learn anything, as well as to enable re-use of scripts.

A simple CLI will display a prompt, accept a command line typed by the user terminated by the <a href="Enter_key" title="Enter key">Enter key</a>, then execute the specified command and provide textual display of results or error messages. Advanced CLIs will validate, interpret and parameter-expand the command line before executing the specified command, and optionally capture or redirect its output.

Unlike a button or menu item in a GUI, a command line is typically self-documenting,<a href="#cite_note-18">[18]</a> stating exactly what the user wants done. In addition, command lines usually include many <a href="Default_(computer_science)" title="Default (computer science)">defaults</a> that can be changed to customize the results. Useful command lines can be saved by assigning a <a href="Character_string" class="mw-redirect" title="Character string">character string</a> or <a href="Alias_(command)" title="Alias (command)">alias</a> to represent the full command, or several commands can be grouped to perform a more complex sequence – for instance, compile the program, install it, and run it — creating a single entity, called a command procedure or script which itself can be treated as a command. These advantages mean that a user must figure out a complex command or series of commands only once, because they can be saved, to be used again.

The commands given to a CLI shell are often in one of the following forms:

<ul><li><code>doSomething how toFiles</code></li>

<li><code>doSomething how sourceFile destinationFile</code></li>

<li><code>doSomething how < inputFile > outputFile</code></li>

<li><code>doSomething how | doSomething how | doSomething how > outputFile</code></li></ul>

where doSomething is, in effect, a <a href="Verb" title="Verb">verb</a>, how an <a href="Adverb" title="Adverb">adverb</a> (for example, should the command be executed verbosely or quietly) and toFiles an object or objects (typically one or more files) on which the command should act. The <code>></code> in the third example is a redirection operator, telling the command-line interpreter to send the output of the command not to its own standard output (the screen) but to the named file. This will overwrite the file. Using <code>>></code> will redirect the output and append it to the file. Another redirection operator is the <a href="Vertical_bar" title="Vertical bar">vertical bar</a> (<code>|</code>), which creates a <a href="Pipeline_(Unix)" title="Pipeline (Unix)">pipeline</a> where the output of one command becomes the input to the next command.<a href="#cite_note-19">[19]</a>

<div class="mw-heading mw-heading3"><h3 id="CLI_and_resource_protection">CLI and resource protection</h3></div>

On some systems, such as <a href="Unix-like" title="Unix-like">Unix-like</a> systems or Windows, one can modify the set of available commands by modifying which paths appear in the <a href="PATH_(variable)" title="PATH (variable)">PATH</a> environment variable or its equivalent. On Unix-like systems, commands also need be marked as <a href="Executable" title="Executable">executable</a> files. The directories in the path variable are searched in the order they are given. By re-ordering the path, one can run e.g. \OS2\MDOS\E.EXE instead of \OS2\E.EXE, when the default is the opposite. Renaming of the executables also works: people often rename their favourite editor to EDIT, for example.

The command line allows one to restrict available commands, such as access to advanced internal commands. The <a href="Bourne_shell" title="Bourne shell">Bourne shell</a> and workalikes such as <a href="Bash_(Unix_shell)" title="Bash (Unix shell)">Bash</a> can be run as a <a href="Restricted_shell" title="Restricted shell">restricted shell</a>; among other things, this prohibits the user from modifying the PATH environment variable, so that if PATH is set to include only directories that contain only permissible commands, the user will only be able to run those commands. The Windows <a href="CMD.EXE" class="mw-redirect" title="CMD.EXE">CMD.EXE</a> also supports restricting available commands. Often, shareware programs will limit the range of commands, including printing a command 'your administrator has disabled running batch files' from the prompt.

Some CLIs, such as those in <a href="Network_router" class="mw-redirect" title="Network router">network routers</a>, have a hierarchy of <a href="Mode_(user_interface)" title="Mode (user interface)">modes</a>, with a different set of commands supported in each mode. The set of commands are grouped by association with security, system, interface, etc. In these systems the user might traverse through a series of sub-modes. For example, if the CLI had two modes called interface and system, the user might use the command interface to enter the interface mode. At this point, commands from the system mode may not be accessible until the user exits the interface mode and enters the system mode.

<div class="mw-heading mw-heading3"><h3 id="Command_prompt">Command prompt</h3></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hatnote{font-style:italic}.mw-parser-output div.hatnote{padding-left:1.6em;margin-bottom:0.5em}.mw-parser-output .hatnote i{font-style:normal}.mw-parser-output .hatnote+link+.hatnote{margin-top:-0.5em}@media print{body.ns-0 .mw-parser-output .hatnote{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><div role="note" class="hatnote navigation-not-searchable">"Command prompt" redirects here. For the Windows component named Command Prompt, see <a href="Cmd.exe" title="Cmd.exe">cmd.exe</a>.</div>

A command prompt (or just prompt) is a sequence of (one or more) characters used in a command-line interface to indicate readiness to accept commands. It literally <a href="https://en.wiktionary.org/wiki/prompt" class="extiw external" title="wiktionary:prompt">prompts</a> the user to take action. A prompt usually ends with one of the characters <code>$</code>, <code>%</code>, <code>#</code>,<a href="#cite_note-DR_1978_SID-20">[20]</a><a href="#cite_note-DR_1982_SID86-21">[21]</a> <code>:</code>, <code>></code> or <code>-</code><a href="#cite_note-Paul_1997_NWDOSTIP-22">[22]</a> and often includes other information, such as the path of the current <a href="Working_directory" title="Working directory">working directory</a> and the <a href="Hostname" title="Hostname">hostname</a>.

On many <a href="Unix" title="Unix">Unix</a> and <a href="Unix-like" title="Unix-like">derivative systems</a>, the prompt commonly ends in <code>$</code> or <code>%</code> if the user is a normal user, but in <code>#</code> if the user is a <a href="Superuser" title="Superuser">superuser</a> ("root" in Unix terminology).

End-users can often modify prompts. Depending on the environment, they may include colors, special characters, and other elements (like variables and functions for the current time, user, shell number or working directory) in order, for instance, to make the prompt more informative or visually pleasing, to distinguish sessions on various machines, or to indicate the current level of nesting of commands. On some systems, special tokens in the definition of the prompt can be used to cause external programs to be called by the command-line interpreter while displaying the prompt.

In DOS' COMMAND.COM and in Windows NT's <a href="Cmd.exe" title="Cmd.exe">cmd.exe</a> users can modify the prompt by issuing a <code>PROMPT</code> command or by directly changing the value of the corresponding <code><a href="%25PROMPT%25" class="mw-redirect" title="%PROMPT%">%PROMPT%</a></code> <a href="Environment_variable" title="Environment variable">environment variable</a>. The default of most modern systems, the <code>C:\></code> style is obtained, for instance, with <code>PROMPT $P$G</code>. The default of older DOS systems, <code>C></code> is obtained by just <code>PROMPT</code>, although on some systems this produces the newer <code>C:\></code> style, unless used on floppy drives A: or B:; on those systems <code>PROMPT $N$G</code> can be used to override the automatic default and explicitly switch to the older style.

Many Unix systems feature the <code>$PS1</code> variable (Prompt String 1),<a href="#cite_note-Parker_2011-23">[23]</a> although other variables also may affect the prompt (depending on the <a href="Unix_shell" title="Unix shell">shell</a> used). In the Bash shell, a prompt of the form:

<div class="mw-highlight mw-highlight-lang-bash mw-content-ltr" dir="ltr"><pre>[time] user@host: work_dir $

</pre></div>

could be set by issuing the command

<div class="mw-highlight mw-highlight-lang-bash mw-content-ltr" dir="ltr"><pre>export PS1='[\t] \u@\H: \W $'

</pre></div>

In <a href="Zsh" class="mw-redirect" title="Zsh">zsh</a> the <code>$RPROMPT</code> variable controls an optional prompt on the right-hand side of the display. It is not a real prompt in that the location of text entry does not change. It is used to display information on the same line as the prompt, but right-justified.

In <a href="RISC_OS" title="RISC OS">RISC OS</a> the command prompt is a <code>*</code> symbol, and thus (OS) CLI commands are often referred to as star commands.<a href="#cite_note-Acorn_1992-24">[24]</a> One can also access the same commands from other command lines (such as the <a href="BBC_BASIC" title="BBC BASIC">BBC BASIC</a> command line), by preceding the command with a <code>*</code>.

<div class="mw-heading mw-heading3"><h3 id="Arguments">Arguments</h3></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .ambox{border:1px solid #a2a9b1;border-left:10px solid #36c;background-color:#fbfbfb;box-sizing:border-box}.mw-parser-output .ambox+link+.ambox,.mw-parser-output .ambox+link+style+.ambox,.mw-parser-output .ambox+link+link+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+style+.ambox,.mw-parser-output .ambox+.mw-empty-elt+link+link+.ambox{margin-top:-1px}html body.mediawiki .mw-parser-output .ambox.mbox-small-left{margin:4px 1em 4px 0;overflow:hidden;width:238px;border-collapse:collapse;font-size:88%;line-height:1.25em}.mw-parser-output .ambox-speedy{border-left:10px solid #b32424;background-color:#fee7e6}.mw-parser-output .ambox-delete{border-left:10px solid #b32424}.mw-parser-output .ambox-content{border-left:10px solid #f28500}.mw-parser-output .ambox-style{border-left:10px solid #fc3}.mw-parser-output .ambox-move{border-left:10px solid #9932cc}.mw-parser-output .ambox-protection{border-left:10px solid #a2a9b1}.mw-parser-output .ambox .mbox-text{border:none;padding:0.25em 0.5em;width:100%}.mw-parser-output .ambox .mbox-image{border:none;padding:2px 0 2px 0.5em;text-align:center}.mw-parser-output .ambox .mbox-imageright{border:none;padding:2px 0.5em 2px 0;text-align:center}.mw-parser-output .ambox .mbox-empty-cell{border:none;padding:0;width:1px}.mw-parser-output .ambox .mbox-image-div{width:52px}@media(min-width:720px){.mw-parser-output .ambox{margin:0 10%}}@media print{body.ns-0 .mw-parser-output .ambox{display:none!important}}

/* end https://en.wikipedia.org/ */

</style>

A command-line argument or <a href="Parameter#Computing" title="Parameter">parameter</a> is an item of information provided to a program when it is started.<a href="#cite_note-25">[25]</a> A program can have many command-line arguments that identify sources or destinations of information, or that alter the operation of the program.

When a command processor is active a program is typically invoked by typing its name followed by command-line arguments (if any). For example, in <a href="Unix" title="Unix">Unix</a> and <a href="Unix-like" title="Unix-like">Unix-like</a> environments, an example of a command-line argument is:

<div class="mw-highlight mw-highlight-lang-bash mw-content-ltr" dir="ltr"><pre>rm file.s

</pre></div>

<code class="mw-highlight mw-highlight-lang-text mw-content-ltr" style="" dir="ltr">file.s</code> is a command-line argument which tells the program <a href="Rm_(Unix)" title="Rm (Unix)">rm</a> to remove the file named <code class="mw-highlight mw-highlight-lang-text mw-content-ltr" style="" dir="ltr">file.s</code>.

Some programming languages, such as <a href="C_(programming_language)" title="C (programming language)">C</a>, <a href="C%2B%2B" title="C++">C++</a> and <a href="Java_(programming_language)" title="Java (programming language)">Java</a>, allow a program to interpret the command-line arguments by handling them as string parameters in the <a href="Main_function" class="mw-redirect" title="Main function">main function</a>.<a href="#cite_note-26">[26]</a><a href="#cite_note-27">[27]</a> Other languages, such as <a href="Python_(programming_language)" title="Python (programming language)">Python</a>, expose operating system specific <a href="API" title="API">API</a> (functionality) through <code>sys</code> <a href="Modular_programming" title="Modular programming">module</a>, and in particular <code>sys.argv</code> for command-line arguments.

In <a href="Unix-like_operating_system" class="mw-redirect" title="Unix-like operating system">Unix-like operating systems</a>, a single hyphen used in place of a file name is a special value specifying that a program should handle data coming from the <a href="Standard_input" class="mw-redirect" title="Standard input">standard input</a> or send data to the <a href="Standard_output" class="mw-redirect" title="Standard output">standard output</a>.

<div class="mw-heading mw-heading4"><h4 id="Command-line_option">Command-line option</h4></div>

A command-line option or simply option (also known as a flag or switch) modifies the operation of a command; the effect is determined by the command's program. Options follow the command name on the command line, separated by spaces. A space before the first option is not always required, such as <code>Dir/?</code> and <code style="white-space:nowrap">DIR /?</code> in DOS, which have the same effect<a href="#cite_note-Paul_1997_NWDOSTIP-22">[22]</a> of listing the DIR command's available options, whereas <code>dir --help</code> (in many versions of Unix) does require the option to be preceded by at least one space (and is case-sensitive).

The format of options varies widely between operating systems. In most cases, the syntax is by convention rather than an operating system requirement; the entire command line is simply a string passed to a program, which can process it in any way the programmer wants, so long as the interpreter can tell where the command name ends and its arguments and options begin.

A few representative samples of command-line options, all relating to listing files in a directory, to illustrate some conventions:

<th>Operating system</th>

<th>Command</th>

<th>Valid alternative</th>

<th>Notes

</th></tr>

<tr>

<td><a href="OpenVMS" title="OpenVMS">OpenVMS</a></td>

<td><code>directory/owner</code></td>

<td><code>Dir /Owner</code></td>

<td>instruct the directory command to also display the ownership of the files. Note the Directory command name is not case sensitive, and can be abbreviated to as few letters as required to remain unique.

</td></tr>

<tr>

<td>Windows</td>

<td>display ownership of files whose names begin with d (or D), sorted by size, smallest first. Note spaces around argument d* are required.

</td></tr>

<tr>

<td><a href="Unix-like" title="Unix-like">Unix-like</a> systems</td>

<td>display in long format files and directories whose names begin with D (but not d), sorted by size (largest first). Note spaces are required around all arguments and options, but some can be run together, e.g. -lS is the same as -l -S.

</td></tr>

<tr>

<td><a href="Data_General_RDOS" title="Data General RDOS">Data General RDOS</a> <a href="Data_General_RDOS#RDOS_CLI" title="Data General RDOS">CLI</a></td>

<td>list every attribute for files created before 26 April 1980. Note the /B at the end of the date argument is a local switch, that modifies the meaning of that argument, while /S and /E are global switches, i.e. apply to the whole command.

</td></tr>

<tr>

<td><code>LISTFILE (FULLDATE)</code></td>

<td>includes the date the file was last written in the list. Note the LISTFILE command name is not case sensitive, and can be abbreviated to as few letters as required to remain unique.

</td></tr></tbody></table>

<div class="mw-heading mw-heading5"><h5 id="Abbreviating_commands">Abbreviating commands</h5></div>

<div role="note" class="hatnote navigation-not-searchable">See also: <a href="Tab_completion" class="mw-redirect" title="Tab completion">Tab completion</a></div>

In <a href="Multics" title="Multics">Multics</a>, command-line options and subsystem keywords may be abbreviated. This idea appears to derive from the <a href="PL/I_programming_language" class="mw-redirect" title="PL/I programming language">PL/I programming language</a>, with its shortened keywords (e.g., STRG for STRINGRANGE and DCL for DECLARE). For example, in the Multics forum subsystem, the -long_subject parameter can be abbreviated -lgsj. It is also common for Multics commands to be abbreviated, typically corresponding to the initial letters of the words that are strung together with underscores to form command names, such as the use of did for delete_iacl_dir.

In some other systems abbreviations are automatic, such as permitting enough of the first characters of a command name to uniquely identify it (such as <code>SU</code> as an abbreviation for <code>SUPERUSER</code>) while others may have some specific abbreviations pre-programmed (e.g. <code>MD</code> for <code><a href="MKDIR" class="mw-redirect" title="MKDIR">MKDIR</a></code> in COMMAND.COM) or user-defined via batch scripts and <a href="Alias_(command)" title="Alias (command)">aliases</a> (e.g. <code>alias md mkdir</code> in <a href="Tcsh" title="Tcsh">tcsh</a>).

<div class="mw-heading mw-heading5"><h5 id="Option_conventions_in_DOS,_Windows,_OS/2">Option conventions in DOS, Windows, OS/2</h5></div>

On DOS, OS/2 and Windows, different programs called from their COMMAND.COM or CMD.EXE (or internal their commands) may use different syntax within the same operating system. For example:

<ul><li>Options may be indicated by either of the switch characters: <code>/</code>, <code>-</code>, or either may be allowed. See below.</li>

<li>They may or may not be <a href="Case-sensitive" class="mw-redirect" title="Case-sensitive">case-sensitive</a>.</li>

<li>Sometimes options and their arguments are run together, sometimes separated by whitespace, and sometimes by a character, typically <code>:</code> or <code>=</code>; thus <code>Prog -fFilename</code>, <code>Prog -f Filename</code>, <code>Prog -f:Filename</code>, <code>Prog -f=Filename</code>.</li>

<li>Some programs allow single-character options to be combined;<a href="#cite_note-Paul_1997_NWDOSTIP-22">[22]</a> others do not. The switch <code>-fA</code> may mean the same as <code>-f -A</code>,<a href="#cite_note-Paul_1997_NWDOSTIP-22">[22]</a> or it may be incorrect, or it may even be a valid but different parameter.</li></ul>

In <a href="DOS" title="DOS">DOS</a>, <a href="OS/2" title="OS/2">OS/2</a> and <a href="Windows" class="mw-redirect" title="Windows">Windows</a>, the forward slash (<code>/</code>) is most prevalent, although the hyphen-minus is also sometimes used. In many versions of DOS (MS-DOS/PC DOS 2.xx and higher, all versions of <a href="DR-DOS" title="DR-DOS">DR-DOS</a> since 5.0, as well as <a href="PTS-DOS" title="PTS-DOS">PTS-DOS</a>, <a href="Embedded_DOS" class="mw-redirect" title="Embedded DOS">Embedded DOS</a>, <a href="FreeDOS" title="FreeDOS">FreeDOS</a> and <a href="RxDOS" class="mw-redirect" title="RxDOS">RxDOS</a>) the switch character (sometimes abbreviated switchar or switchchar) to be used is defined by a value returned from a <a href="System_call" title="System call">system call</a> (<a href="INT_21h" class="mw-redirect" title="INT 21h">INT 21h</a>/AX=3700h). The default character returned by this API is <code>/</code>, but can be changed to a hyphen-minus on the above-mentioned systems, except for under Datalight ROM-DOS and MS-DOS/PC DOS 5.0 and higher, which always return <code>/</code> from this call (unless one of many available <a href="Terminate-and-stay-resident_program" title="Terminate-and-stay-resident program">TSRs</a> to reenable the SwitChar feature is loaded). In some of these systems (MS-DOS/PC DOS 2.xx, DOS Plus 2.1, DR-DOS 7.02 and higher, PTS-DOS, Embedded DOS, FreeDOS and RxDOS), the setting can also be pre-configured by a <a href="SWITCHAR_(CONFIG.SYS_directive)" class="mw-redirect" title="SWITCHAR (CONFIG.SYS directive)">SWITCHAR</a> directive in <a href="CONFIG.SYS" title="CONFIG.SYS">CONFIG.SYS</a>. General Software's Embedded DOS provides a SWITCH command for the same purpose, whereas <a href="4DOS" title="4DOS">4DOS</a> allows the setting to be changed via <code>SETDOS /W:n</code>.<a href="#cite_note-4DOS_8.00_HELP-28">[28]</a> Under DR-DOS, if the setting has been changed from <code>/</code>, the first directory separator <code>\</code> in the display of the <a href="PROMPT_(DOS_command)" class="mw-redirect" title="PROMPT (DOS command)">PROMPT</a> parameter <code>$G</code> will change to a forward slash <code>/</code> (which is also a valid directory separator in DOS, FlexOS, 4680 OS, 4690 OS, OS/2 and Windows) thereby serving as a visual clue to indicate the change.<a href="#cite_note-Paul_1997_NWDOSTIP-22">[22]</a> Also, the current setting is reflected also in the built-in help screens.<a href="#cite_note-Paul_1997_NWDOSTIP-22">[22]</a> Some versions of DR-DOS <a href="COMMAND.COM" title="COMMAND.COM">COMMAND.COM</a> also support a PROMPT token <code>$/</code> to display the current setting. COMMAND.COM since DR-DOS 7.02 also provides a <a href="Pseudo-environment_variable" class="mw-redirect" title="Pseudo-environment variable">pseudo-environment variable</a> named <code><a href="%25/%25" class="mw-redirect" title="%/%">%/%</a></code> to allow portable batchjobs to be written.<a href="#cite_note-Caldera_1998_DELTREE101-29">[29]</a><a href="#cite_note-Caldera_1998_NEW703-30">[30]</a> Several external DR-DOS commands additionally support an <a href="Environment_variable" title="Environment variable">environment variable</a> <code><a href="%25SWITCHAR%25" class="mw-redirect" title="%SWITCHAR%">%SWITCHAR%</a></code> to override the system setting.

However, many programs are hardwired to use <code>/</code> only, rather than retrieving the switch setting before parsing command-line arguments. A very small number, mainly ports from Unix-like systems, are programmed to accept <code>-</code> even if the switch character is not set to it (for example <code><a href="Netstat" title="Netstat">netstat</a></code> and <code><a href="Ping_(networking_utility)" title="Ping (networking utility)">ping</a></code>, supplied with <a href="Microsoft_Windows" title="Microsoft Windows">Microsoft Windows</a>, will accept the /? option to list available options, and yet the list will specify the <code>-</code> convention).

<div class="mw-heading mw-heading5"><h5 id="Option_conventions_in_Unix-like_systems">Option conventions in Unix-like systems</h5></div>

In <a href="Unix-like" title="Unix-like">Unix-like</a> systems, the ASCII <a href="Hyphen-minus" title="Hyphen-minus">hyphen-minus</a> begins options; the new (and <a href="GNU" title="GNU">GNU</a>) convention is to use two hyphens then a word (e.g. <code>--create</code>) to identify the option's use while the old convention (and still available as an option for frequently used options) is to use one hyphen then one letter (e.g., <code>-c</code>); if one hyphen is followed by two or more letters it may mean two options are being specified, or it may mean the second and subsequent letters are a parameter (such as filename or date) for the first option.<a href="#cite_note-31">[31]</a>

Two hyphen-minus characters without following letters (<code>--</code>) may indicate that the remaining arguments should not be treated as options, which is useful for example if a file name itself begins with a hyphen, or if further arguments are meant for an inner command (e.g., <a href="Sudo" title="Sudo">sudo</a>). Double hyphen-minuses are also sometimes used to prefix long options where more descriptive option names are used. This is a common feature of <a href="GNU" title="GNU">GNU</a> software. The <a href="Getopt" title="Getopt">getopt</a> function and program, and the <a href="Getopts" title="Getopts">getopts</a> command are usually used for parsing command-line options.

Unix command names, arguments and options are case-sensitive (except in a few examples, mainly where popular commands from other operating systems have been ported to Unix).

<div class="mw-heading mw-heading5"><h5 id="Option_conventions_in_other_systems">Option conventions in other systems</h5></div>

<a href="FlexOS" title="FlexOS">FlexOS</a>, <a href="4680_OS" class="mw-redirect" title="4680 OS">4680 OS</a> and <a href="4690_OS" class="mw-redirect" title="4690 OS">4690 OS</a> use <code>-</code>.

<a href="CP/M" title="CP/M">CP/M</a> typically used <code>[</code>.

<a href="Conversational_Monitor_System" title="Conversational Monitor System">Conversational Monitor System</a> (CMS) uses a single <a href="Bracket#Parentheses" title="Bracket">left parenthesis</a> to separate options at the end of the command from the other arguments. For example, in the following command the options indicate that the target file should be replaced if it exists, and the date and time of the source file should be retained on the copy:

<code>COPY source file a target file b (REPLACE OLDDATE)</code>

<a href="Data_General" title="Data General">Data General</a>'s CLI under their <a href="Data_General_RDOS" title="Data General RDOS">RDOS</a>, <a href="Data_General_AOS" title="Data General AOS">AOS</a>, etc. operating systems, as well as the version of CLI that came with their <a href="Business_Basic" title="Business Basic">Business Basic</a>, uses only <code>/</code> as the switch character, is case-insensitive, and allows local switches on some arguments to control the way they are interpreted, such as <code>MAC/U LIB/S A B C $LPT/L</code> has the global option <code class="mw-highlight mw-highlight-lang-text mw-content-ltr" style="" dir="ltr">U</code> to the macro assembler command to append user symbols, but two local switches, one to specify LIB should be skipped on pass 2 and the other to direct listing to the printer, $LPT.

<div class="mw-heading mw-heading3"><h3 id="Built-in_usage_help">Built-in usage help</h3></div>

<div role="note" class="hatnote navigation-not-searchable">See also: <a href="Help_(command)" title="Help (command)">help (command)</a></div>

One of the criticisms of a CLI is the lack of cues to the user as to the available actions. In contrast, GUIs usually inform the user of available actions with menus, icons, or other visual cues. To overcome this limitation, many CLI programs display a <a href="Usage_message" title="Usage message">usage message</a>, typically when invoked with no arguments or one of <code>?</code>, <code>-?</code>, <code>-h</code>, <code>-H</code>, <code>/?</code>, <code>/h</code>, <code>/H</code>, <code>/Help</code>, <code>-help</code>, or <code>--help</code>.<a href="#cite_note-Paul_1997_NWDOSTIP-22">[22]</a><a href="#cite_note-Paul_2002_CPI-32">[32]</a><a href="#cite_note-Paul_2002_DEBUG-33">[33]</a>

However, entering a program name without parameters in the hope that it will display usage help can be hazardous, as programs and scripts for which command line arguments are optional will execute without further notice.

Although desirable at least for the help parameter, programs may not support all option lead-in characters exemplified above.

Under DOS, where the default <a href="#Option_conventions_in_DOS.2C_Windows.2C_OS.2F2">command-line option character</a> can be changed from <code>/</code> to <code>-</code>, programs may query the <a href="SwitChar" class="mw-redirect" title="SwitChar">SwitChar</a> API in order to determine the current setting. So, if a program is not hardwired to support them all, a user may need to know the current setting even to be able to reliably request help.

If the SwitChar has been changed to <code>-</code> and therefore the <code>/</code> character is accepted as alternative path delimiter also at the DOS command line, programs may misinterpret options like <code>/h</code> or <code>/H</code> as paths rather than help parameters.<a href="#cite_note-Paul_1997_NWDOSTIP-22">[22]</a> However, if given as first or only parameter, most DOS programs will, by convention, accept it as request for help regardless of the current SwitChar setting.<a href="#cite_note-Paul_1997_NWDOSTIP-22">[22]</a><a href="#cite_note-4DOS_8.00_HELP-28">[28]</a>

In some cases, different levels of help can be selected for a program. Some programs supporting this allow to give a verbosity level as an optional argument to the help parameter (as in <code>/H:1</code>, <code>/H:2</code>, etc.) or they give just a short help on help parameters with question mark and a longer help screen for the other help options.<a href="#cite_note-Paul_2006_FreeKEYB-34">[34]</a>

Depending on the program, additional or more specific help on accepted parameters is sometimes available by either providing the parameter in question as an argument to the help parameter or vice versa (as in <code>/H:W</code> or in <code>/W:?</code> (assuming <code>/W</code> would be another parameter supported by the program)).<a href="#cite_note-CCI_1997_HELP-35">[35]</a><a href="#cite_note-Paul_1997_DRDOSTIP-36">[36]</a><a href="#cite_note-Paul_2002_DEBUG-33">[33]</a><a href="#cite_note-Paul_2002_CPI-32">[32]</a><a href="#cite_note-Paul_2006_FreeKEYB-34">[34]</a><a href="#cite_note-NB1-37">[nb 1]</a>

In a similar fashion to the help parameter, but much less common, some programs provide additional information about themselves (like mode, status, version, author, license or contact information) when invoked with an about parameter like <code>-!</code>, <code>/!</code>, <code>-about</code>, or <code>--about</code>.<a href="#cite_note-Paul_2002_CPI-32">[32]</a>

Since the <code>?</code> and <code>!</code> characters typically also serve other purposes at the command line, they may not be available in all scenarios, therefore, they should not be the only options to access the corresponding help information.

If more detailed help is necessary than provided by a program's built-in internal help, many systems support a dedicated external <code><a href="Help_(command)" title="Help (command)">help</a> command</code>" command (or similar), which accepts a command name as calling parameter and will invoke an external help system.

In the DR-DOS family, typing <code>/?</code> or <code>/H</code> at the <a href="COMMAND.COM" title="COMMAND.COM">COMMAND.COM</a> prompt instead of a command itself will display a dynamically generated list of available internal commands;<a href="#cite_note-Paul_1997_NWDOSTIP-22">[22]</a> <a href="4DOS" title="4DOS">4DOS</a> and <a href="NDOS" class="mw-redirect" title="NDOS">NDOS</a> support the same feature by typing <code>?</code> at the prompt<a href="#cite_note-4DOS_8.00_HELP-28">[28]</a> (which is also accepted by newer versions of DR-DOS COMMAND.COM); internal commands can be individually disabled or reenabled via <code>SETDOS /I</code>.<a href="#cite_note-4DOS_8.00_HELP-28">[28]</a> In addition to this, some newer versions of DR-DOS COMMAND.COM also accept a <code>?%</code> command to display a list of available built-in <a href="DR-DOS_system_information_variable" class="mw-redirect" title="DR-DOS system information variable">pseudo-environment variables</a>. Besides their purpose as quick help reference this can be used in batchjobs to query the facilities of the underlying command-line processor.<a href="#cite_note-Paul_1997_NWDOSTIP-22">[22]</a>

<div class="mw-heading mw-heading3"><h3 id="Command_description_syntax">Command description syntax</h3></div>

Built-in usage help and <a href="Man_page" title="Man page">man pages</a> commonly employ a small syntax to describe the valid command form:<a href="#cite_note-OpenGroup_2008-38">[37]</a><a href="#cite_note-Microsoft_2005_Shell-39">[38]</a><a href="#cite_note-Microsoft_2010_Syntax-40">[39]</a><a href="#cite_note-NB2-41">[nb 2]</a>

<ul><li>angle brackets for required parameters: <code>ping <hostname></code></li>

<li>square brackets for optional parameters: <code>mkdir [-p] <dirname></code></li>

<li>ellipses for repeated items: <code>cp <source1> [source2…] <dest></code></li>

<li>vertical bars for choice of items: <code>netstat {-t|-u}</code></li></ul>

Notice that these characters have different meanings than when used directly in the shell. Angle brackets may be omitted when confusing the parameter name with a literal string is not likely.

<div class="mw-heading mw-heading3"><h3 id="The_space_character">The space character</h3></div>

In many areas of computing, but particularly in the command line, the <a href="Space_character" class="mw-redirect" title="Space character">space character</a> can cause problems as it has two distinct and incompatible functions: as part of a command or parameter, or as a parameter or name <a href="Delimiter" title="Delimiter">separator</a>. Ambiguity can be prevented either by prohibiting embedded spaces in file and directory names in the first place (for example, by substituting them with <a href="Underscores" class="mw-redirect" title="Underscores">underscores</a> <code>_</code>), or by enclosing a name with embedded spaces between quote characters or using an <a href="Escape_character" title="Escape character">escape character</a> before the space, usually a <a href="Backslash" title="Backslash">backslash</a> (<code>\</code>). For example

<dl><dd><code>Long path/Long program name Parameter one Parameter two</code> …</dd></dl>

is ambiguous (is program name part of the program name, or two parameters?); however

<dl><dd><code>Long_path/Long_program_name Parameter_one Parameter_two</code> …,</dd>

<dd><code>LongPath/LongProgramName ParameterOne ParameterTwo</code> …,</dd>

<dd><code>"Long path/Long program name" "Parameter one" "Parameter two"</code> …</dd></dl>

and

<dl><dd><code>Long\ path/Long\ program\ name Parameter\ one Parameter\ two</code> …</dd></dl>

are not ambiguous. <a href="Unix" title="Unix">Unix</a>-based operating systems minimize the use of embedded spaces to minimize the need for quotes. In <a href="Microsoft_Windows" title="Microsoft Windows">Microsoft Windows</a>, one often has to use quotes because embedded spaces (such as in directory names) are common.

<div class="mw-heading mw-heading2"><h2 id="Command-line_interpreter">Command-line interpreter</h2></div>

<div role="note" class="hatnote navigation-not-searchable">See also: <a href="List_of_command-line_interpreters" title="List of command-line interpreters">List of command-line interpreters</a></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .templatequote{overflow:hidden;margin:1em 0;padding:0 32px}.mw-parser-output .templatequotecite{line-height:1.5em;text-align:left;margin-top:0}@media(min-width:500px){.mw-parser-output .templatequotecite{padding-left:1.6em}}

/* end https://en.wikipedia.org/ */

</style><blockquote class="templatequote">Although most users think of the shell as an interactive command interpreter, it is really a programming language in which each statement runs a command. Because it must satisfy both the interactive and programming aspects of command execution, it is a strange language, shaped as much by history as by design.</blockquote><div class="templatequotecite">— <a href="Brian_W._Kernighan" class="mw-redirect" title="Brian W. Kernighan">Brian W. Kernighan</a> & <a href="Rob_Pike" title="Rob Pike">Rob Pike</a><a href="#cite_note-Kerninghan_1984-42">[40]</a></div>

The term command-line interpreter is applied to <a href="Computer_program" title="Computer program">computer programs</a> designed to <a href="Interpreter_(computing)" title="Interpreter (computing)">interpret</a> a sequence of lines of text which may be entered by a user, read from a file or another kind of <a href="Data_stream" title="Data stream">data stream</a>. The context of interpretation is usually one of a given <a href="Operating_system" title="Operating system">operating system</a> or <a href="Programming_language" title="Programming language">programming language</a>.

Command-line interpreters allow users to issue various commands in a very efficient (and often terse) way. This requires the user to know the names of the commands and their parameters, and the syntax of the <a href="Programming_language" title="Programming language">language</a> that is interpreted.

The Unix <a href="Shebang_(Unix)" title="Shebang (Unix)"><code>#!</code></a> mechanism and OS/2 EXTPROC command facilitate the passing of batch files to external processors. One can use these mechanisms to write specific command processors for dedicated uses, and process external data files which reside in batch files.

Many graphical interfaces, such as the OS/2 <a href="Presentation_Manager" title="Presentation Manager">Presentation Manager</a> and early versions of Microsoft Windows use command lines to call helper programs to open documents and programs. The commands are stored in the graphical shell or in files like the registry or the <a href="OS/2" title="OS/2">OS/2</a> <code>OS2USER.INI</code> file.

<div class="mw-heading mw-heading3"><h3 id="Early_history">Early history</h3></div>

The earliest computers did not support interactive input/output devices, often relying on <a href="Sense_switch" title="Sense switch">sense switches</a> and lights to communicate with the <a href="Computer_operator" title="Computer operator">computer operator</a>. This was adequate for <a href="Batch_processing" title="Batch processing">batch</a> systems that ran one program at a time, often with the programmer acting as operator. This also had the advantage of low overhead, since lights and switches could be tested and set with one machine instruction. Later a single <a href="System_console" class="mw-redirect" title="System console">system console</a> was added to allow the operator to communicate with the system.

From the 1960s onwards, user interaction with computers was primarily by means of command-line interfaces, initially on machines like the <a href="Teletype_Model_33" title="Teletype Model 33">Teletype Model 33</a> ASR, but then on early <a href="Cathode_ray_tube" class="mw-redirect" title="Cathode ray tube">CRT</a>-based <a href="Computer_terminals" class="mw-redirect" title="Computer terminals">computer terminals</a> such as the <a href="VT52" title="VT52">VT52</a>.

All of these devices were purely text based, with no ability to display graphic or pictures.<a href="#cite_note-NB3-43">[nb 3]</a> For business <a href="Application_program" class="mw-redirect" title="Application program">application programs</a>, text-based <a href="Menu_(computing)" title="Menu (computing)">menus</a> were used, but for more general interaction the command line was the interface.

Around 1964 <a href="Louis_Pouzin" title="Louis Pouzin">Louis Pouzin</a> introduced the concept and the name shell in <a href="Multics" title="Multics">Multics</a>, building on earlier, simpler facilities in the <a href="Compatible_Time-Sharing_System" title="Compatible Time-Sharing System">Compatible Time-Sharing System</a> (CTSS).<a href="#cite_note-Pouzin-44">[41]</a>

From the early 1970s the <a href="Unix" title="Unix">Unix</a> operating system adapted the concept of a powerful command-line environment, and introduced the ability to <a href="Pipeline_(Unix)" title="Pipeline (Unix)">pipe</a> the output of one command in as input to another. Unix also had the capability to save and re-run strings of commands as <a href="Shell_scripts" class="mw-redirect" title="Shell scripts">shell scripts</a> which acted like custom commands.

The command line was also the main interface for the early home computers such as the <a href="Commodore_PET" title="Commodore PET">Commodore PET</a>, <a href="Apple_II" title="Apple II">Apple II</a> and <a href="BBC_Micro" title="BBC Micro">BBC Micro</a> – almost always in the form of a <a href="BASIC" title="BASIC">BASIC</a> interpreter. When more powerful business-oriented microcomputers arrived with <a href="CP/M" title="CP/M">CP/M</a> and later <a href="DOS" title="DOS">DOS</a> computers such as the <a href="IBM_PC" class="mw-redirect" title="IBM PC">IBM PC</a>, the command line began to borrow some of the syntax and features of the Unix shells such as <a href="Globbing" class="mw-redirect" title="Globbing">globbing</a> and <a href="Pipeline_(Unix)" title="Pipeline (Unix)">piping</a> of output.

The command line was first seriously challenged by the <a href="PARC_(company)" title="PARC (company)">PARC</a> <a href="GUI" class="mw-redirect" title="GUI">GUI</a> approach used in the 1983 <a href="Apple_Lisa" title="Apple Lisa">Apple Lisa</a> and the 1984 <a href="Apple_Macintosh" class="mw-redirect" title="Apple Macintosh">Apple Macintosh</a>. A few computer users used GUIs such as <a href="GEOS_(16-bit_operating_system)" title="GEOS (16-bit operating system)">GEOS</a> and <a href="Windows_3.1" title="Windows 3.1">Windows 3.1</a> but the majority of <a href="IBM_PC" class="mw-redirect" title="IBM PC">IBM PC</a> users did not replace their <a href="COMMAND.COM" title="COMMAND.COM">COMMAND.COM</a> shell with a GUI until <a href="Windows_95" title="Windows 95">Windows 95</a> was released in 1995.<a href="#cite_note-Betanews-45">[42]</a><a href="#cite_note-Microsoft_History-46">[43]</a>

<div class="mw-heading mw-heading3"><h3 id="Modern_usage_as_an_operating_system_shell">Modern usage as an operating system shell</h3></div>

While most non-expert computer users now use a GUI almost exclusively, more advanced users have access to powerful command-line environments:

<ul><li>The default VAX/VMS command shell, using the <a href="DIGITAL_Command_Language" title="DIGITAL Command Language">DCL</a> language, has been ported to Windows systems at least three times, including PC-DCL and Acceler8 DCL Lite. Unix command shells have been ported to VMS and DOS/Windows 95 and Windows NT types of operating systems.</li>

<li><a href="COMMAND.COM" title="COMMAND.COM">COMMAND.COM</a> is the command-line interpreter of <a href="MS-DOS" title="MS-DOS">MS-DOS</a>, <a href="IBM_PC_DOS" title="IBM PC DOS">IBM PC DOS</a>, and clones such as <a href="DR-DOS" title="DR-DOS">DR-DOS</a>, <a href="SISNE_plus" title="SISNE plus">SISNE plus</a>, <a href="PTS-DOS" title="PTS-DOS">PTS-DOS</a>, <a href="ROM-DOS" class="mw-redirect" title="ROM-DOS">ROM-DOS</a>, and <a href="FreeDOS" title="FreeDOS">FreeDOS</a>.</li>

<li>Windows <a href="Resource_Kit" title="Resource Kit">Resource Kit</a> and <a href="Windows_Services_for_UNIX" title="Windows Services for UNIX">Windows Services for UNIX</a> include Korn and the Bourne shells along with a Perl interpreter (Services for UNIX contains <a href="ActiveState" title="ActiveState">ActiveState</a> <a href="ActivePerl" title="ActivePerl">ActivePerl</a> in later versions and <a href="Interix" title="Interix">Interix</a> for versions 1 and 2 and a shell compiled by Microsoft)</li>

<li>IBM OS/2 (and derivatives such as <a href="EComStation" title="EComStation">eComStation</a> and <a href="ArcaOS" title="ArcaOS">ArcaOS</a>) has the <a href="Cmd.exe" title="Cmd.exe">cmd.exe</a> processor. This copies the <a href="COMMAND.COM" title="COMMAND.COM">COMMAND.COM</a> commands, with extensions to <a href="REXX" class="mw-redirect" title="REXX">REXX</a>.</li>

<li>cmd.exe is part of the <a href="Windows_NT" title="Windows NT">Windows NT</a> stream of operating systems.</li>

<li>Yet another cmd.exe is a stripped-down shell for <a href="Windows_CE" title="Windows CE">Windows CE</a> 3.0.</li>

<li>An MS-DOS type interpreter called PocketDOS has been ported to Windows CE machines; the most recent release is almost identical to MS-DOS 6.22 and can also run Windows 1, 2, and 3.0, <a href="QBasic" title="QBasic">QBasic</a> and other development tools, 4NT and 4DOS. The latest release includes several shells, namely MS-DOS 6.22, PC DOS 7, DR DOS 3.xx, and others.</li>

<li>Windows users might use the <a href="CScript" class="mw-redirect" title="CScript">CScript</a> interface to alternate programs, from the command line. <a href="PowerShell" title="PowerShell">PowerShell</a> provides a command-line interface, but its applets are not written in <a href="Shell_script" title="Shell script">Shell script</a>. Implementations of the <a href="Unix_shell" title="Unix shell">Unix shell</a> are also available as part of the <a href="Microsoft_POSIX_subsystem" title="Microsoft POSIX subsystem">POSIX sub-system</a>,<a href="#cite_note-Microsoft_POSIX-47">[44]</a> <a href="Cygwin" title="Cygwin">Cygwin</a>, <a href="MKS_Toolkit" title="MKS Toolkit">MKS Toolkit</a>, <a href="UWIN" title="UWIN">UWIN</a>, <a href="Hamilton_C_shell" title="Hamilton C shell">Hamilton C shell</a> and other software packages. Available shells for these interoperability tools include <a href="C_shell" title="C shell">csh</a>, <a href="KornShell" title="KornShell">ksh</a>, <a href="Bourne_shell" title="Bourne shell">sh</a>, Bash, <a href="Restricted_shell" title="Restricted shell">rsh</a>, <a href="Tclsh" class="mw-redirect" title="Tclsh">tclsh</a> and less commonly <a href="Zsh" class="mw-redirect" title="Zsh">zsh</a>, psh</li>

<li>Implementations of <a href="PHP" title="PHP">PHP</a> have a shell for interactive use called php-cli.</li>

<li>Standard <a href="Tcl/Tk" class="mw-redirect" title="Tcl/Tk">Tcl/Tk</a> has two interactive shells, Tclsh and Wish, the latter being the GUI version.</li>

<li><a href="Python_(programming_language)" title="Python (programming language)">Python</a>, <a href="Ruby_(programming_language)" title="Ruby (programming language)">Ruby</a>, <a href="Lua_(programming_language)" class="mw-redirect" title="Lua (programming language)">Lua</a>, <a href="XLNT" title="XLNT">XLNT</a>, and other interpreters also have command shells for interactive use.</li>

<li><a href="FreeBSD" title="FreeBSD">FreeBSD</a> uses <a href="Tcsh" title="Tcsh">tcsh</a> as its default interactive shell for the <a href="Superuser" title="Superuser">superuser</a>, and <a href="Almquist_shell" title="Almquist shell">ash</a> as default scripting shell.</li>

<li>Many <a href="Linux_distribution" title="Linux distribution">Linux distributions</a> have the Bash implementation of the <a href="Unix_shell" title="Unix shell">Unix shell</a>.</li>

<li>Apple <a href="MacOS" title="MacOS">macOS</a> and some Linux distributions use <a href="Zsh" class="mw-redirect" title="Zsh">zsh</a>. Previously, macOS used <a href="Tcsh" title="Tcsh">tcsh</a> and Bash.</li>

<li><a href="Embedded_Linux" class="mw-redirect" title="Embedded Linux">Embedded Linux</a> (and other embedded <a href="Unix-like" title="Unix-like">Unix-like</a>) devices often use the <a href="Almquist_shell" title="Almquist shell">Ash</a> implementation of the Unix shell, as part of <a href="Busybox" class="mw-redirect" title="Busybox">Busybox</a>.</li>

<li><a href="Android_(operating_system)" title="Android (operating system)">Android</a> uses the <a href="KornShell" title="KornShell">mksh</a> shell,<a href="#cite_note-Android_mksh-48">[45]</a><a href="#cite_note-Android_adb-49">[46]</a> which replaces a shell derived from <a href="Almquist_shell" title="Almquist shell">ash</a><a href="#cite_note-Android_sh-50">[47]</a> that was used in older Android versions, supplemented with commands from the separate toolbox<a href="#cite_note-Android_Toolbox-51">[48]</a> binary.</li>

<li><a href="HarmonyOS" title="HarmonyOS">HarmonyOS</a>, <a href="OpenHarmony" title="OpenHarmony">OpenHarmony</a> and Oniro uses the commands from third party toolbox compatibility system attached to Linux kernel of the subsystem alongside default Shell with exec commands.<a href="#cite_note-52">[49]</a><a href="#cite_note-53">[50]</a></li>

<li>Routers with <a href="Cisco_IOS" title="Cisco IOS">Cisco IOS</a>,<a href="#cite_note-Cisco_IOS-54">[51]</a> <a href="Junos" class="mw-redirect" title="Junos">Junos</a><a href="#cite_note-Juniper-55">[52]</a> and many others are commonly configured from the command line.</li>

<li>The <a href="Plan_9_from_Bell_Labs" title="Plan 9 from Bell Labs">Plan 9</a> operating system uses the <a href="Rc_(Unix_shell)" title="Rc (Unix shell)">rc</a> shell, which is similar in design to the <a href="Unix_shell#Bourne_shell" title="Unix shell">Bourne</a> shell.</li></ul>

<div class="mw-heading mw-heading2"><h2 id="Scripting">Scripting</h2></div>

Most command-line interpreters support <a href="Script_(computer_programming)" class="mw-redirect" title="Script (computer programming)">scripting</a>, to various extents. (They are, after all, interpreters of an <a href="Interpreted_programming_language" class="mw-redirect" title="Interpreted programming language">interpreted programming language</a>, albeit in many cases the language is unique to the particular command-line interpreter.) They will interpret scripts (variously termed <a href="Shell_script" title="Shell script">shell scripts</a> or <a href="Batch_file" title="Batch file">batch files</a>) written in the <a href="Programming_language" title="Programming language">language</a> that they interpret. Some command-line interpreters also incorporate the interpreter engines of other languages, such as <a href="REXX" class="mw-redirect" title="REXX">REXX</a>, in addition to their own, allowing the executing of scripts, in those languages, directly within the command-line interpreter itself.

Conversely, <a href="Scripting_programming_language" class="mw-redirect" title="Scripting programming language">scripting programming languages</a>, in particular those with an <a href="Eval" title="Eval">eval</a> <a href="Function_(programming)" class="mw-redirect" title="Function (programming)">function</a> (such as REXX, <a href="Perl" title="Perl">Perl</a>, <a href="Python_(programming_language)" title="Python (programming language)">Python</a>, <a href="Ruby_(programming_language)" title="Ruby (programming language)">Ruby</a> or <a href="Jython" title="Jython">Jython</a>), can be used to implement command-line interpreters and filters. For a few <a href="Operating_system" title="Operating system">operating systems</a>, most notably <a href="DOS" title="DOS">DOS</a>, such a command interpreter provides a more flexible command-line interface than the one supplied. In other cases, such a command interpreter can present a highly customised user interface employing the user interface and input/output facilities of the language.

<div class="mw-heading mw-heading2"><h2 id="Other_command-line_interfaces">Other command-line interfaces</h2></div>

The command line provides an interface between programs as well as the user. In this sense, a command line is an alternative to a <a href="Dialog_box" title="Dialog box">dialog box</a>. Editors and databases present a command line, in which alternate command processors might run. On the other hand, one might have options on the command line, which opens a dialog box. The latest version of 'Take Command' has this feature. DBase used a dialog box to construct command lines, which could be further edited before use.

Programs like BASIC, <a href="Diskpart" title="Diskpart">diskpart</a>, <a href="Edlin" title="Edlin">Edlin</a>, and QBASIC all provide command-line interfaces, some of which use the system shell. Basic is modeled on the default interface for 8-bit Intel computers. Calculators can be run as command-line or dialog interfaces.

<a href="Emacs" title="Emacs">Emacs</a> provides a command-line interface in the form of its minibuffer. Commands and arguments can be entered using Emacs standard text editing support, and output is displayed in another buffer.

There are a number of text mode games, like <a href="Colossal_Cave_Adventure" title="Colossal Cave Adventure">Adventure</a> or <a href="King's_Quest#Series" title="King's Quest">King's Quest 1-3</a>, which relied on the user typing commands at the bottom of the screen. One controls the character by typing commands like 'get ring' or 'look'. The program returns a text which describes how the character sees it, or makes the action happen. The <a href="Text_adventure" class="mw-redirect" title="Text adventure">text adventure</a> <a href="The_Hitchhiker's_Guide_to_the_Galaxy_(video_game)" title="The Hitchhiker's Guide to the Galaxy (video game)">The Hitchhiker's Guide to the Galaxy</a>, a piece of <a href="Interactive_fiction" title="Interactive fiction">interactive fiction</a> based on <a href="Douglas_Adams" title="Douglas Adams">Douglas Adam's</a> book of the same name, is a teletype-style command-line game.

The most notable of these interfaces is the <a href="Standard_streams" title="Standard streams">standard streams</a> interface, which allows the output of one command to be passed to the input of another. Text files can serve either purpose as well. This provides the interfaces of piping, filters and redirection. Under Unix, <a href="Everything_is_a_file" title="Everything is a file">devices are files</a> too, so the normal type of file for the shell used for stdin, stdout and stderr is a <a href="Teleprinter#Teleprinters_in_computing" title="Teleprinter">tty</a> device file.

Another command-line interface allows a shell program to launch helper programs, either to launch documents or start a program. The command is processed internally by the shell, and then passed on to another program to launch the document. The graphical interface of Windows and OS/2 rely heavily on command lines passed through to other programs – console or graphical, which then usually process the command line without presenting a user-console.

Programs like the OS/2 <a href="E_(PC_DOS)" title="E (PC DOS)">E editor</a> and some other IBM <a href="Text_editor" title="Text editor">editors</a>, can process command lines normally meant for the shell, the output being placed directly in the document window.

A web browser's URL input field can be used as a command line. It can be used to launch <a href="Web_app" class="mw-redirect" title="Web app">web apps</a>, <a href="About%3Aconfig" class="mw-redirect" title="About:config">access browser configuration</a>, as well as perform a search. <a href="Google" title="Google">Google</a>, which has been called "the command line of the internet" will perform a domain-specific search when it detects search parameters in a known format.<a href="#cite_note-Google-56">[53]</a> This functionality is present whether the search is triggered from a browser field or on Google's website.

There are <a href="JavaScript" title="JavaScript">JavaScript</a> libraries that allow to write command line applications in browser as standalone Web apps or as part of bigger application.<a href="#cite_note-57">[54]</a> An example of such a website is the CLI interface to <a href="DuckDuckGo" title="DuckDuckGo">DuckDuckGo</a>.<a href="#cite_note-58">[55]</a> There are also <a href="Web-based_SSH" title="Web-based SSH">web-based SSH</a> applications that allow access to a server’s command-line interface from a browser.

Many PC <a href="Video_games" class="mw-redirect" title="Video games">video games</a> feature a command line interface often referred to as a console. It is typically used by the game developers during development and by mod developers for debugging purposes as well as for cheating or skipping parts of the game.

<ul><li><a href="Comparison_of_command_shells" title="Comparison of command shells">Comparison of command shells</a></li>

<li><a href="List_of_command-line_interpreters" title="List of command-line interpreters">List of command-line interpreters</a></li>

<li><a href="Console_application" title="Console application">Console application</a></li>

<li><a href="Interpreter_directive" class="mw-redirect" title="Interpreter directive">Interpreter directive</a></li>

<li><a href="Read-eval-print_loop" class="mw-redirect" title="Read-eval-print loop">Read-eval-print loop</a></li>

<li><a href="Shell_script" title="Shell script">Shell script</a></li>

<li><a href="Run_command" title="Run command">Run command</a></li>

<li><a href="Graphical_user_interface#Comparison_to_other_interfaces" title="Graphical user interface">Graphical user interface § Comparison to other interfaces</a></li>

<li><a href="In_the_Beginning..._Was_the_Command_Line" title="In the Beginning... Was the Command Line">In the Beginning... Was the Command Line</a></li></ul>

<div class="mw-heading mw-heading2"><h2 id="Notes">Notes</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist">

<li id="cite_note-NB1-37"><a href="#cite_ref-NB1_37-0">^</a> An example is the comprehensive internal help system of the <a href="DR-DOS_7.03" class="mw-redirect" title="DR-DOS 7.03">DR-DOS 7.03</a> <a href="DEBUG" class="mw-redirect" title="DEBUG">DEBUG</a> command, which can be invoked via <code>??</code> at the debug prompt (rather than only the default <code>?</code> overview). Specific help pages can be selected via <code>?n</code> (where <code>n</code> is the number of the page). Additionally, help for specific commands can be displayed by specifying the command name after <code>?</code>, f.e. <code>?D</code> will invoke help for the various dump commands (like <code>D</code> etc.). Some of these features were already supported by the <a href="DR_DOS_3.41" class="mw-redirect" title="DR DOS 3.41">DR DOS 3.41</a> SID86 and GEMSID.

</li>

<li id="cite_note-NB2-41"><a href="#cite_ref-NB2_41-0">^</a> Notable difference for describing the command syntax of <a href="DOS" title="DOS">DOS</a>-like operating systems: Windows Server 2003 R2 documentation uses italic letters for "information that the user must supply", but Windows Server 2008 documentation uses angle brackets. Italics can not be displayed by the internal help command, while there is no problem with angle brackets.

</li>

<li id="cite_note-NB3-43"><a href="#cite_ref-NB3_43-0">^</a> With the exception of <a href="ASCII_art" title="ASCII art">ASCII art</a>.

</li>

</ol></div></div>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://sqlite.org/cli.html">"Command Line Shell For SQLite"</a>.</cite>

</li>

<li id="cite_note-2"><a href="#cite_ref-2">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://apereo.github.io/cas/7.0.x/installation/Configuring-Commandline-Shell.html">"CAS - Configuring Commandline Shell"</a>.</cite>

</li>

<li id="cite_note-3"><a href="#cite_ref-3">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.contentstack.com/blog/tech-talk/the-evolution-of-command-line-interface-cli-a-historical-insight">"The evolution of command line interface (CLI): A historical insight | Contentstack"</a>. www.contentstack.com. Retrieved 2025-01-28.</cite>

</li>

<li id="cite_note-Unix_Shells-4"><a href="#cite_ref-Unix_Shells_4-0">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20071108064620/http://www.linuxfinances.info/info/unixshells.html">"Unix Shells"</a>. Archived from <a rel="nofollow" class="external text" href="http://linuxfinances.info/info/unixshells.html">the original</a> on 2007-11-08. <q>the notion of having a replaceable "command shell" rather than a "monitor" tightly integrated with the OS kernel tends to be attributed to Multics.</q></cite>

</li>

<li id="cite_note-multicians-5">^ <a href="#cite_ref-multicians_5-0">a</a> <a href="#cite_ref-multicians_5-1">b</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.multicians.org/shell.html">"The Origin of the Shell"</a>. www.multicians.org. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20171221142542/http://www.multicians.org/shell.html">Archived</a> from the original on 2017-12-21. Retrieved 2017-04-12.</cite>

</li>

<li id="cite_note-Metz_2013-6"><a href="#cite_ref-Metz_2013_6-0">^</a> <cite id="CITEREFMetz2013" class="citation magazine cs1">Metz, Cade (2013-01-03). <a rel="nofollow" class="external text" href="https://www.wired.com/2013/01/louis_pouzin_internet_hall/">"Say Bonjour to the Internet's Long-Lost French Uncle"</a>. <a href="Wired_(magazine)" title="Wired (magazine)">Wired</a>. Retrieved 2017-07-31.</cite>

</li>

<li id="cite_note-Mazieres_2004-7"><a href="#cite_ref-Mazieres_2004_7-0">^</a> <cite id="CITEREFMazières2004" class="citation web cs1">Mazières, David (Fall 2004). <a rel="nofollow" class="external text" href="http://www.scs.stanford.edu/nyu/04fa/notes/l4d.txt">"MULTICS - The First Seven Years"</a>. Advanced Operating Systems. Stanford Computer Science Department. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20141123000315/http://www.scs.stanford.edu/nyu/04fa/notes/l4d.txt">Archived</a> from the original on 2014-11-23. Retrieved 2017-08-01.</cite>

</li>

<li id="cite_note-ibm-8">^ <a href="#cite_ref-ibm_8-0">a</a> <a href="#cite_ref-ibm_8-1">b</a> <cite id="CITEREFJones2011" class="citation web cs1">Jones, M. (2011-12-06). <a rel="nofollow" class="external text" href="https://www.ibm.com/developerworks/library/l-linux-shells/">"Evolution of shells in Linux"</a>. developerWorks. <a href="IBM" title="IBM">IBM</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20170708215831/https://www.ibm.com/developerworks/library/l-linux-shells/">Archived</a> from the original on 2017-07-08. Retrieved 2017-08-01.</cite>

</li>

<li id="cite_note-9"><a href="#cite_ref-9">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://kartsci.org/kocomu/computer-history/graphical-user-interface-history/">"Graphical User Interface History"</a>. KASS. Retrieved 2024-03-24.</cite>

</li>

<li id="cite_note-10"><a href="#cite_ref-10">^</a> <cite id="CITEREFSingh2006" class="citation book cs1">Singh, Amit (2006-06-19). <a rel="nofollow" class="external text" href="https://books.google.com/books?id=K8vUkpOXhN4C&dq=macos+was+based+on+darwin&pg=PR7">Mac OS X Internals: A Systems Approach</a>. Addison-Wesley Professional. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-13-270226-3</bdi>.</cite>

</li>

<li id="cite_note-11"><a href="#cite_ref-11">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://docs.python.org/3/using/cmdline.html">"1. Command line and environment"</a>. Python documentation. Retrieved 2024-08-05.</cite>

</li>

<li id="cite_note-12"><a href="#cite_ref-12">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://aws.amazon.com/what-is/cli/#:~:text=You%20can%20use%20a%20command,benefit%20from%20using%20the%20CLI.">"What is a CLI? - Command Line Interface Explained - AWS"</a>. Amazon Web Services, Inc. Retrieved 2025-01-28.</cite>

</li>

<li id="cite_note-Bash-13"><a href="#cite_ref-Bash_13-0">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.gnu.org/software/bash/manual/bashref.html#Shell-Commands">"GNU BASH Reference"</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20101203065719/https://www.gnu.org/software/bash/manual/bashref.html#Shell-Commands">Archived</a> from the original on 2010-12-03. Retrieved 2015-12-20.</cite>

</li>

<li id="cite_note-Microsoft_Windows-14"><a href="#cite_ref-Microsoft_Windows_14-0">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://technet.microsoft.com/en-us/library/bb490954.aspx">"Microsoft Windows Command Shell Overview"</a>. 2009-09-11. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20150905103923/https://technet.microsoft.com/en-us/library/bb490954.aspx">Archived</a> from the original on 2015-09-05. Retrieved 2015-07-12.</cite>

</li>

<li id="cite_note-15"><a href="#cite_ref-15">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://linuxhandbook.com/shell-builtin-commands/">"Shell Built-in Commands List"</a>. Linux Handbook. 2023-07-05. Retrieved 2024-08-05.</cite>

</li>

<li id="cite_note-16"><a href="#cite_ref-16">^</a> <cite id="CITEREFB" class="citation web cs1">B, Jason. <a rel="nofollow" class="external text" href="https://opensource.com/article/17/6/set-path-linux">"How to set your $PATH variable in Linux | Opensource.com"</a>. opensource.com. Retrieved 2024-08-05.</cite>

</li>

<li id="cite_note-17"><a href="#cite_ref-17">^</a> <cite id="CITEREFJasonGerend2023" class="citation web cs1">JasonGerend (2023-02-03). <a rel="nofollow" class="external text" href="https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/path">"path"</a>. learn.microsoft.com. Retrieved 2024-08-05.</cite>

</li>

<li id="cite_note-18"><a href="#cite_ref-18">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://tutorials.cloudfoundry.org/cf4devs/getting-started/cli/#:~:text=Documentation,the%20most%20frequently%20used%20commands">"Command Line Interface (CLI)"</a>. tutorials.cloudfoundry.org. Retrieved 2025-01-28.</cite>

</li>

<li id="cite_note-19"><a href="#cite_ref-19">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.oreilly.com/library/view/learning-the-bash/1565923472/">"Learning the bash Shell, Second Edition [Book]"</a>. www.oreilly.com. Retrieved 2024-08-05.</cite>

</li>

<li id="cite_note-DR_1978_SID-20"><a href="#cite_ref-DR_1978_SID_20-0">^</a> <cite class="citation book cs1"><a rel="nofollow" class="external text" href="http://www.cpm.z80.de/randyfiles/DRI/SID_ZSID.pdf">SID Users Guide</a> (PDF). <a href="Digital_Research" title="Digital Research">Digital Research</a>. 1978. 595-2549. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20191020124044/http://www.cpm.z80.de/randyfiles/DRI/SID_ZSID.pdf">Archived</a> (PDF) from the original on 2019-10-20. Retrieved 2020-02-06.</cite> (4+69 pages)

</li>

<li id="cite_note-DR_1982_SID86-21"><a href="#cite_ref-DR_1982_SID86_21-0">^</a> <cite class="citation book cs1"><a rel="nofollow" class="external text" href="http://www.cpm.z80.de/manuals/SID86_User_Guide.txt">SID-86 User's Guide for CP/M-86</a> (2 ed.). <a href="Digital_Research" title="Digital Research">Digital Research</a>. August 1982 [March 1982]. SID86UG.WS4. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20191020123025/http://www.cpm.z80.de/manuals/SID86_User_Guide.txt">Archived</a> from the original on 2019-10-20. Retrieved 2020-02-06.</cite> <a rel="nofollow" class="external autonumber" href="https://web.archive.org/web/20200208055456/https://archive.computerhistory.org/resources/access/text/2016/12/102762507-05-01-acc.pdf">[1]</a> (NB. A retyped version of the manual by Emmanuel Roche with Q, SR, and Z commands added.)

</li>

<li id="cite_note-Paul_1997_NWDOSTIP-22">^ <a href="#cite_ref-Paul_1997_NWDOSTIP_22-0">a</a> <a href="#cite_ref-Paul_1997_NWDOSTIP_22-1">b</a> <a href="#cite_ref-Paul_1997_NWDOSTIP_22-2">c</a> <a href="#cite_ref-Paul_1997_NWDOSTIP_22-3">d</a> <a href="#cite_ref-Paul_1997_NWDOSTIP_22-4">e</a> <a href="#cite_ref-Paul_1997_NWDOSTIP_22-5">f</a> <a href="#cite_ref-Paul_1997_NWDOSTIP_22-6">g</a> <a href="#cite_ref-Paul_1997_NWDOSTIP_22-7">h</a> <a href="#cite_ref-Paul_1997_NWDOSTIP_22-8">i</a> <a href="#cite_ref-Paul_1997_NWDOSTIP_22-9">j</a> <a href="#cite_ref-Paul_1997_NWDOSTIP_22-10">k</a> <cite id="CITEREFPaul1997" class="citation web cs1 cs1-prop-foreign-lang-source">Paul, Matthias R. (1997-07-30). <a rel="nofollow" class="external text" href="http://www.antonis.de/dos/dos-tuts/mpdostip/html/nwdostip.htm">"NWDOS-TIPs – Tips & Tricks rund um Novell DOS 7, mit Blick auf undokumentierte Details, Bugs und Workarounds"</a>. MPDOSTIP. Release 157 (in German) (3 ed.). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20170910194752/http://www.antonis.de/dos/dos-tuts/mpdostip/html/nwdostip.htm">Archived</a> from the original on 2017-09-10. Retrieved 2014-09-06.</cite> (NB. NWDOSTIP.TXT is a comprehensive work on <a href="Novell_DOS_7" class="mw-redirect" title="Novell DOS 7">Novell DOS 7</a> and <a href="OpenDOS_7.01" class="mw-redirect" title="OpenDOS 7.01">OpenDOS 7.01</a>, including the description of many undocumented features and internals. It is part of the author's yet larger MPDOSTIP.ZIP collection maintained up to 2001 and distributed on many sites at the time. The provided link points to a HTML-converted older version of the NWDOSTIP.TXT file.)

</li>

<li id="cite_note-Parker_2011-23"><a href="#cite_ref-Parker_2011_23-0">^</a> <cite id="CITEREFParker2011" class="citation book cs1">Parker, Steve (2011). "Chapter 11: Choosing and using shells". <a rel="nofollow" class="external text" href="https://books.google.com/books?id=wWjqCF9HLfYC">Shell Scripting: Expert Recipes for Linux, Bash and more</a>. Programmer to programmer. Indianapolis, USA: <a href="John_Wiley_%26_Sons" class="mw-redirect" title="John Wiley & Sons">John Wiley & Sons</a>. p. 262. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-111816632-1</bdi>. <q>The shell has four different command prompts, called PS1, P52, P53, and PS4. PS stands for Prompt String.</q></cite>

</li>

<li id="cite_note-Acorn_1992-24"><a href="#cite_ref-Acorn_1992_24-0">^</a> <cite class="citation book cs1"><a rel="nofollow" class="external text" href="http://www.4corn.co.uk/_archive/docs/RISC%20OS%203%20User%20Guide%20(3.0)-opt.pdf">RISC OS 3 User Guide</a> (PDF). <a href="Acorn_Computers_Limited" class="mw-redirect" title="Acorn Computers Limited">Acorn Computers Limited</a>. 1992-03-01. p. 125. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20170109183207/http://www.4corn.co.uk/_archive/docs/RISC%20OS%203%20User%20Guide%20(3.0)-opt.pdf">Archived</a> (PDF) from the original on 2017-01-09. Retrieved 2017-04-12.</cite>

</li>

<li id="cite_note-25"><a href="#cite_ref-25">^</a> <cite id="CITEREFnguyen-dows2024" class="citation web cs1">nguyen-dows (2024-05-29). <a rel="nofollow" class="external text" href="https://learn.microsoft.com/en-us/windows/terminal/command-line-arguments">"Windows Terminal command line arguments"</a>. learn.microsoft.com. Retrieved 2024-08-05.</cite>

</li>

<li id="cite_note-26"><a href="#cite_ref-26">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.w3schools.in/c-programming/command-line-arguments">"Command Line Arguments in C"</a>. www.w3schools.in. Retrieved 2024-08-05.</cite>

</li>

<li id="cite_note-27"><a href="#cite_ref-27">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.geeksforgeeks.org/command-line-arguments-in-java/">"Command Line Arguments in Java"</a>. GeeksforGeeks. 2016-08-16. Retrieved 2024-08-05.</cite>

</li>

<li id="cite_note-4DOS_8.00_HELP-28">^ <a href="#cite_ref-4DOS_8.00_HELP_28-0">a</a> <a href="#cite_ref-4DOS_8.00_HELP_28-1">b</a> <a href="#cite_ref-4DOS_8.00_HELP_28-2">c</a> <a href="#cite_ref-4DOS_8.00_HELP_28-3">d</a> <cite id="CITEREFBrothersRawsonConnPaul2002" class="citation book cs1">Brothers, Hardin; <a href="Tom_Rawson" class="mw-redirect" title="Tom Rawson">Rawson, Tom</a>; <a href="Rex_C._Conn" class="mw-redirect" title="Rex C. Conn">Conn, Rex C.</a>; Paul, Matthias R.; Dye, Charles E.; Georgiev, Luchezar I. (2002-02-27). <a href="4DOS_8.00" class="mw-redirect" title="4DOS 8.00">4DOS 8.00 online help</a>.</cite>

</li>

<li id="cite_note-Caldera_1998_DELTREE101-29"><a href="#cite_ref-Caldera_1998_DELTREE101_29-0">^</a> <cite id="CITEREFPaul1998" class="citation book cs1">Paul, Matthias R. (1998-01-09). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20190408145354/http://www.lookas.net/ftp/incoming/darbui/Justas/DRDOS/DELTREE.BAT">DELTREE.BAT R1.01 Extended file and directory delete</a>. <a href="Caldera%2C_Inc." class="mw-redirect" title="Caldera, Inc.">Caldera, Inc.</a> Archived from <a rel="nofollow" class="external text" href="http://www.lookas.net/ftp/incoming/darbui/Justas/DRDOS/DELTREE.BAT">the original</a> on 2019-04-08. Retrieved 2019-04-08.</cite>

</li>

<li id="cite_note-Caldera_1998_NEW703-30"><a href="#cite_ref-Caldera_1998_NEW703_30-0">^</a> <cite class="citation book cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20190408142232/http://www.lookas.net/ftp/incoming/darbui/Justas/DRDOS/WHATSNEW.TXT">DR-DOS 7.03 WHATSNEW.TXT — Changes from DR-DOS 7.02 to DR-DOS 7.03</a>. <a href="Caldera%2C_Inc." class="mw-redirect" title="Caldera, Inc.">Caldera, Inc.</a> 1998-12-24. Archived from <a rel="nofollow" class="external text" href="http://www.lookas.net/ftp/incoming/darbui/Justas/DRDOS/WHATSNEW.TXT">the original</a> on 2019-04-08. Retrieved 2019-04-08.</cite>

</li>

<li id="cite_note-31"><a href="#cite_ref-31">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.gnu.org/software/libc/manual/html_node/Argument-Syntax.html">"Argument Syntax (The GNU C Library)"</a>. gnu.org. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20210618184837/https://www.gnu.org/software/libc/manual/html_node/Argument-Syntax.html">Archived</a> from the original on 2021-06-18. Retrieved 2021-07-09.</cite>

</li>

<li id="cite_note-Paul_2002_CPI-32">^ <a href="#cite_ref-Paul_2002_CPI_32-0">a</a> <a href="#cite_ref-Paul_2002_CPI_32-1">b</a> <a href="#cite_ref-Paul_2002_CPI_32-2">c</a> <cite id="CITEREFPaul2002" class="citation web cs1">Paul, Matthias R. (2002-05-13). <a rel="nofollow" class="external text" href="https://marc.info/?l=freedos-dev&m=102133580113139&w=2">"[fd-dev] mkeyb"</a>. freedos-dev. <a rel="nofollow" class="external text" href="https://archive.today/20180910213410/https://marc.info/?l=freedos-dev&m=102133580113139&w=2">Archived</a> from the original on 2018-09-10. Retrieved 2018-09-10. <q>[…] CPI /H […] CPI [@] [@] [/?|/Help[:topic]] [/!|/About] […] [?|&] […] /?, /Help Display this help screen or specific help for a topic (+) […] /!, /About Display the 'About' info screen […] /Cpifile (+) .CPI/.CP file name <EGA.CPI>; extension: <.CPI>; CPI.EXE=StdIn […] /Report Report file name <'<s></s>'=StdOut>; extension: <.RPT> […] /Style (+) Export <0>-6=BIN-raw/ROM/RAM/PSF0/1/SH/CHED; 7-12/13-18/19-24=ASM-hex/dec/bin/ip/il/p/l/mp/ml […] CPI /H:C […] Overview on codepage file parameter usage: […] CPI /H:S […] Overview on /Style parameters: […] ?, & Online edit mode (prompts for additional parameter input) […]</q></cite>

</li>

<li id="cite_note-Paul_2002_DEBUG-33">^ <a href="#cite_ref-Paul_2002_DEBUG_33-0">a</a> <a href="#cite_ref-Paul_2002_DEBUG_33-1">b</a> <cite id="CITEREFPaul2002" class="citation newsgroup cs1">Paul, Matthias R. (2002-01-09). <a rel="nofollow" class="external text" href="https://groups.google.com/d/msg/comp.os.cpm/KG4R7ZNvHK8/U5LAkmjcxYgJ">"SID86"</a>. <a href="Usenet_newsgroup" title="Usenet newsgroup">Newsgroup</a>: <a rel="nofollow" class="external text" href="news:comp.os.cpm">comp.os.cpm</a>. Retrieved 2018-04-08. <q>[…] Since the <a href="DR-DOS_7.03" class="mw-redirect" title="DR-DOS 7.03">DR-DOS 7.03</a> <a href="DEBUG" class="mw-redirect" title="DEBUG">DEBUG</a> is still based on the old SID86.EXE, I suggest to run DEBUG 1.51 and enter the extended help system with ?? from the debug prompt. This will give you eight screens full of syntax and feature help. Some of these features were also supported by older issues. […]</q></cite>

</li>

<li id="cite_note-Paul_2006_FreeKEYB-34">^ <a href="#cite_ref-Paul_2006_FreeKEYB_34-0">a</a> <a href="#cite_ref-Paul_2006_FreeKEYB_34-1">b</a> <cite id="CITEREFPaulFrinke2006" class="citation book cs1">Paul, Matthias R.; Frinke, Axel C. (2006-01-16). FreeKEYB - Advanced international DOS keyboard and console driver (User Manual) (v7 preliminary ed.).</cite>

</li>

<li id="cite_note-CCI_1997_HELP-35"><a href="#cite_ref-CCI_1997_HELP_35-0">^</a> <cite class="citation book cs1">CCI Multiuser DOS 7.22 GOLD Online Documentation. <a href="Concurrent_Controls%2C_Inc." class="mw-redirect" title="Concurrent Controls, Inc.">Concurrent Controls, Inc.</a> (CCI). 1997-02-10. HELP.HLP.</cite> (NB. The symbolic instruction debugger SID86 provides a short help screen on <code>?</code> and comprehensive help on <code>??</code>.)

</li>

<li id="cite_note-Paul_1997_DRDOSTIP-36"><a href="#cite_ref-Paul_1997_DRDOSTIP_36-0">^</a> <cite id="CITEREFPaul1997" class="citation web cs1 cs1-prop-foreign-lang-source">Paul, Matthias R. (1997-05-24) [1991]. <a rel="nofollow" class="external text" href="http://www.antonis.de/dos/dos-tuts/mpdostip/html/drdostip.htm">"DRDOSTIP.TXT – Tips und Tricks für DR DOS 3.41 - 5.0"</a>. MPDOSTIP (in German) (47 ed.). <a rel="nofollow" class="external text" href="https://web.archive.org/web/20161107125452/http://www.antonis.de/dos/dos-tuts/mpdostip/html/drdostip.htm">Archived</a> from the original on 2016-11-07. Retrieved 2016-11-07.</cite>

</li>

<li id="cite_note-OpenGroup_2008-38"><a href="#cite_ref-OpenGroup_2008_38-0">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap12.html">"The Open Group Base Specifications Issue 7, Chapter 12.1 Utility Argument Syntax"</a>. <a href="The_Open_Group" title="The Open Group">The Open Group</a>. 2008. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20130430125310/http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap12.html">Archived</a> from the original on 2013-04-30. Retrieved 2013-04-07.</cite><code><a rel="nofollow" class="external text" href="https://linux.die.net/man/7/man-pages">man-pages(7)</a></code> – <a href="Linux" title="Linux">Linux</a> Conventions and Miscellany <a href="Man_page" title="Man page">Manual</a> (NB. Conventions for describing commands on Unix-like operating systems.)

</li>

<li id="cite_note-Microsoft_2005_Shell-39"><a href="#cite_ref-Microsoft_2005_Shell_39-0">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://technet.microsoft.com/en-us/library/cc737438.aspx">"Command shell overview"</a>. Windows Server 2003 Product Help. <a href="Microsoft" title="Microsoft">Microsoft</a>. 2005-01-21. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20120712200546/http://technet.microsoft.com/en-us/library/cc737438.aspx">Archived</a> from the original on 2012-07-12. Retrieved 2013-04-07.</cite>

</li>

<li id="cite_note-Microsoft_2010_Syntax-40"><a href="#cite_ref-Microsoft_2010_Syntax_40-0">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://technet.microsoft.com/en-us/library/cc771080.aspx">"Command-Line Syntax Key"</a>. Windows Server 2008 R2 TechNet Library. <a href="Microsoft" title="Microsoft">Microsoft</a>. 2010-01-25. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20130504221131/http://technet.microsoft.com/en-us/library/cc771080.aspx">Archived</a> from the original on 2013-05-04. Retrieved 2013-04-07.</cite>

</li>

<li id="cite_note-Kerninghan_1984-42"><a href="#cite_ref-Kerninghan_1984_42-0">^</a> <cite id="CITEREFKernighanPike1984" class="citation book cs1"><a href="Brian_Kernighan" title="Brian Kernighan">Kernighan, Brian W.</a>; <a href="Rob_Pike" title="Rob Pike">Pike, Rob</a> (1984). <a rel="nofollow" class="external text" href="https://archive.org/details/unixprogramminge0000kern">The UNIX Programming Environment</a>. Englewood Cliffs: <a href="Prentice-Hall" class="mw-redirect" title="Prentice-Hall">Prentice-Hall</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>0-13-937699-2</bdi>.</cite>

</li>

<li id="cite_note-Pouzin-44"><a href="#cite_ref-Pouzin_44-0">^</a> <cite id="CITEREFPouzin" class="citation web cs1">Pouzin, Louis. <a rel="nofollow" class="external text" href="http://www.multicians.org/shell.html">"The Origin of the Shell"</a>. Multicians.org. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20171221142542/http://www.multicians.org/shell.html">Archived</a> from the original on 2017-12-21. Retrieved 2013-09-22.</cite>

</li>

<li id="cite_note-Betanews-45"><a href="#cite_ref-Betanews_45-0">^</a> <cite id="CITEREFWilcox2010" class="citation web cs1">Wilcox, Joe (2010-08-24). <a rel="nofollow" class="external text" href="http://betanews.com/2010/08/24/remembering-windows-95-s-launch-15-years-later/">"Remembering Windows 95's launch 15 years later"</a>. BetaNews. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20150218221032/http://betanews.com/2010/08/24/remembering-windows-95-s-launch-15-years-later/">Archived</a> from the original on 2015-02-18. Retrieved 2015-02-18.</cite>

</li>

<li id="cite_note-Microsoft_History-46"><a href="#cite_ref-Microsoft_History_46-0">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20150301073112/http://windows.microsoft.com/en-US/windows/history">"A history of Windows"</a>. windows.microsoft.com. Archived from <a rel="nofollow" class="external text" href="http://windows.microsoft.com/en-US/windows/history#T1=era0">the original</a> on 2015-03-01.</cite>

</li>

<li id="cite_note-Microsoft_POSIX-47"><a href="#cite_ref-Microsoft_POSIX_47-0">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://technet.microsoft.com/en-us/library/cc754351.aspx">"Windows POSIX shell compatibility"</a>. 2013-02-22. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20170703090254/https://technet.microsoft.com/en-us/library/cc754351.aspx">Archived</a> from the original on 2017-07-03. Retrieved 2017-08-26.</cite>

</li>

<li id="cite_note-Android_mksh-48"><a href="#cite_ref-Android_mksh_48-0">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://android.googlesource.com/platform/external/mksh/+/master">"master - platform/external/mksh - Git at Google"</a>. android.googlesource.com. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20160121112754/https://android.googlesource.com/platform/external/mksh/%2B/master">Archived</a> from the original on 2016-01-21. Retrieved 2018-03-18.</cite>

</li>

<li id="cite_note-Android_adb-49"><a href="#cite_ref-Android_adb_49-0">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://stackoverflow.com/questions/11950131/android-adb-shell-ash-or-ksh">"Android adb shell - ash or ksh?"</a>. stackoverflow.com. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20170702022904/https://stackoverflow.com/questions/11950131/android-adb-shell-ash-or-ksh">Archived</a> from the original on 2017-07-02. Retrieved 2018-03-14.</cite>

</li>

<li id="cite_note-Android_sh-50"><a href="#cite_ref-Android_sh_50-0">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://archive.today/20121217165813/https://github.com/android/platform_system_core/tree/master/sh">"Android sh source"</a>. <a href="GitHub" title="GitHub">GitHub</a>. Archived from <a rel="nofollow" class="external text" href="https://github.com/android/platform_system_core/tree/master/sh">the original</a> on 2012-12-17.</cite>

</li>

<li id="cite_note-Android_Toolbox-51"><a href="#cite_ref-Android_Toolbox_51-0">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://github.com/android/platform_system_core/tree/master/toolbox">"Android toolbox source"</a>. <a href="GitHub" title="GitHub">GitHub</a>.</cite>

</li>

<li id="cite_note-52"><a href="#cite_ref-52">^</a> <cite class="citation cs2"><a rel="nofollow" class="external text" href="https://github.com/openharmony/third_party_toybox">openharmony/third_party_toybox</a>, OpenHarmony, 2021-10-14, retrieved 2024-07-07</cite>

</li>

<li id="cite_note-53"><a href="#cite_ref-53">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.bookstack.cn/read/openharmony-1.0-zh-cn/kernel-Shell%E4%BB%8B%E7%BB%8D.md">"调测 - Shell介绍 - 《华为鸿蒙操作系统(OpenHarmony) v1.0 开发者文档》 - 书栈网 · BookStack"</a>. www.bookstack.cn. Retrieved 2024-07-07.</cite>

</li>

<li id="cite_note-Cisco_IOS-54"><a href="#cite_ref-Cisco_IOS_54-0">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.cisco.com/c/en/us/td/docs/ios/12_2/configfun/configuration/guide/ffun_c/fcf001.html">"Configuration Fundamentals Configuration Guide, Cisco IOS Release 15M&T"</a>. <a href="Cisco" title="Cisco">Cisco</a>. 2013-10-30. Using the Command-Line Interface. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20161118234827/http://www.cisco.com/c/en/us/td/docs/ios/12_2/configfun/configuration/guide/ffun_c/fcf001.html">Archived</a> from the original on 2016-11-18. Retrieved 2016-11-28. <q>The Cisco IOS command-line interface (CLI) is the primary user interface…</q></cite>

</li>

<li id="cite_note-Juniper-55"><a href="#cite_ref-Juniper_55-0">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.juniper.net/techpubs/software/junos/junos55/swconfig55-getting-started/html/cli-overview-getting-started.html">"Command-Line Interface Overview"</a>. www.juniper.net. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20030908113531/http://www.juniper.net/techpubs/software/junos/junos55/swconfig55-getting-started/html/cli-overview-getting-started.html">Archived</a> from the original on 2003-09-08. Retrieved 2018-03-14.</cite>

</li>

<li id="cite_note-Google-56"><a href="#cite_ref-Google_56-0">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://www.knaster.com/2004/04/google_strange_.html">"Google strange goodness"</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20140304185253/http://www.knaster.com/2004/04/google_strange_.html">Archived</a> from the original on 2014-03-04. Retrieved 2014-02-27.</cite>

</li>

<li id="cite_note-57"><a href="#cite_ref-57">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://terminal.jcubic.pl/">"jQuery Terminal Emulator"</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20210420221405/https://terminal.jcubic.pl/">Archived</a> from the original on 2021-04-20. Retrieved 2021-04-20.</cite>

</li>

<li id="cite_note-58"><a href="#cite_ref-58">^</a> <cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://duckduckgo.com/tty/">"DuckDuckGo TTY"</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20210507211818/https://duckduckgo.com/tty/">Archived</a> from the original on 2021-05-07. Retrieved 2021-04-20.</cite>

</li>

</ol></div></div>

<div class="mw-heading mw-heading2"><h2 id="External_links">External links</h2></div>

<ul><li><a rel="nofollow" class="external text" href="http://www.patersontech.com/Dos/Softalk/Softalk.html">The Roots of DOS</a> David Hunter, Softalk for the IBM Personal Computer March 1983. Archived at Patersontech.com since <a rel="nofollow" class="external text" href="https://web.archive.org/web/20001003150623/http://www.patersontech.com/Dos/Softalk/Softalk.html">2000</a>.</li>

<li><a rel="nofollow" class="external text" href="https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/windows-commands">Windows Commands</a>: Microsoft TechNet Database "Command-Line Reference"</li></ul>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hlist dl,.mw-parser-output .hlist ol,.mw-parser-output .hlist ul{margin:0;padding:0}.mw-parser-output .hlist dd,.mw-parser-output .hlist dt,.mw-parser-output .hlist li{margin:0;display:inline}.mw-parser-output .hlist.inline,.mw-parser-output .hlist.inline dl,.mw-parser-output .hlist.inline ol,.mw-parser-output .hlist.inline ul,.mw-parser-output .hlist dl dl,.mw-parser-output .hlist dl ol,.mw-parser-output .hlist dl ul,.mw-parser-output .hlist ol dl,.mw-parser-output .hlist ol ol,.mw-parser-output .hlist ol ul,.mw-parser-output .hlist ul dl,.mw-parser-output .hlist ul ol,.mw-parser-output .hlist ul ul{display:inline}.mw-parser-output .hlist .mw-empty-li{display:none}.mw-parser-output .hlist dt::after{content:": "}.mw-parser-output .hlist dd::after,.mw-parser-output .hlist li::after{content:" · ";font-weight:bold}.mw-parser-output .hlist dd:last-child::after,.mw-parser-output .hlist dt:last-child::after,.mw-parser-output .hlist li:last-child::after{content:none}.mw-parser-output .hlist dd dd:first-child::before,.mw-parser-output .hlist dd dt:first-child::before,.mw-parser-output .hlist dd li:first-child::before,.mw-parser-output .hlist dt dd:first-child::before,.mw-parser-output .hlist dt dt:first-child::before,.mw-parser-output .hlist dt li:first-child::before,.mw-parser-output .hlist li dd:first-child::before,.mw-parser-output .hlist li dt:first-child::before,.mw-parser-output .hlist li li:first-child::before{content:" (";font-weight:normal}.mw-parser-output .hlist dd dd:last-child::after,.mw-parser-output .hlist dd dt:last-child::after,.mw-parser-output .hlist dd li:last-child::after,.mw-parser-output .hlist dt dd:last-child::after,.mw-parser-output .hlist dt dt:last-child::after,.mw-parser-output .hlist dt li:last-child::after,.mw-parser-output .hlist li dd:last-child::after,.mw-parser-output .hlist li dt:last-child::after,.mw-parser-output .hlist li li:last-child::after{content:")";font-weight:normal}.mw-parser-output .hlist ol{counter-reset:listitem}.mw-parser-output .hlist ol>li{counter-increment:listitem}.mw-parser-output .hlist ol>li::before{content:" "counter(listitem)"\a0 "}.mw-parser-output .hlist dd ol>li:first-child::before,.mw-parser-output .hlist dt ol>li:first-child::before,.mw-parser-output .hlist li ol>li:first-child::before{content:" ("counter(listitem)"\a0 "}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1236075235">

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbox{box-sizing:border-box;border:1px solid #a2a9b1;width:100%;clear:both;font-size:88%;text-align:center;padding:1px;margin:1em auto 0}.mw-parser-output .navbox .navbox{margin-top:0}.mw-parser-output .navbox+.navbox,.mw-parser-output .navbox+.navbox-styles+.navbox{margin-top:-1px}.mw-parser-output .navbox-inner,.mw-parser-output .navbox-subgroup{width:100%}.mw-parser-output .navbox-group,.mw-parser-output .navbox-title,.mw-parser-output .navbox-abovebelow{padding:0.25em 1em;line-height:1.5em;text-align:center}.mw-parser-output .navbox-group{white-space:nowrap;text-align:right}.mw-parser-output .navbox,.mw-parser-output .navbox-subgroup{background-color:#fdfdfd}.mw-parser-output .navbox-list{line-height:1.5em;border-color:#fdfdfd}.mw-parser-output .navbox-list-with-group{text-align:left;border-left-width:2px;border-left-style:solid}.mw-parser-output tr+tr>.navbox-abovebelow,.mw-parser-output tr+tr>.navbox-group,.mw-parser-output tr+tr>.navbox-image,.mw-parser-output tr+tr>.navbox-list{border-top:2px solid #fdfdfd}.mw-parser-output .navbox-title{background-color:#ccf}.mw-parser-output .navbox-abovebelow,.mw-parser-output .navbox-group,.mw-parser-output .navbox-subgroup .navbox-title{background-color:#ddf}.mw-parser-output .navbox-subgroup .navbox-group,.mw-parser-output .navbox-subgroup .navbox-abovebelow{background-color:#e6e6ff}.mw-parser-output .navbox-even{background-color:#f7f7f7}.mw-parser-output .navbox-odd{background-color:transparent}.mw-parser-output .navbox .hlist td dl,.mw-parser-output .navbox .hlist td ol,.mw-parser-output .navbox .hlist td ul,.mw-parser-output .navbox td.hlist dl,.mw-parser-output .navbox td.hlist ol,.mw-parser-output .navbox td.hlist ul{padding:0.125em 0}.mw-parser-output .navbox .navbar{display:block;font-size:100%}.mw-parser-output .navbox-title .navbar{float:left;text-align:left;margin-right:0.5em}body.skin--responsive .mw-parser-output .navbox-image img{max-width:none!important}@media print{body.ns-0 .mw-parser-output .navbox{display:none!important}}

/* end https://en.wikipedia.org/ */

</style></div><div role="navigation" class="navbox" aria-labelledby="Operating_systems310" style="padding:3px"><table class="nowraplinks mw-collapsible mw-collapsed navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="2"><style data-mw-deduplicate="TemplateStyles:r1239400231">

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbar{display:inline;font-size:88%;font-weight:normal}.mw-parser-output .navbar-collapse{float:left;text-align:left}.mw-parser-output .navbar-boxtext{word-spacing:0}.mw-parser-output .navbar ul{display:inline-block;white-space:nowrap;line-height:inherit}.mw-parser-output .navbar-brackets::before{margin-right:-0.125em;content:"[ "}.mw-parser-output .navbar-brackets::after{margin-left:-0.125em;content:" ]"}.mw-parser-output .navbar li{word-spacing:-0.125em}.mw-parser-output .navbar a>span,.mw-parser-output .navbar a>abbr{text-decoration:inherit}.mw-parser-output .navbar-mini abbr{font-variant:small-caps;border-bottom:none;text-decoration:none;cursor:inherit}.mw-parser-output .navbar-ct-full{font-size:114%;margin:0 7em}.mw-parser-output .navbar-ct-mini{font-size:114%;margin:0 4em}html.skin-theme-clientpref-night .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}@media(prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}}@media print{.mw-parser-output .navbar{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><div id="Operating_systems310" style="font-size:114%;margin:0 4em"><a href="Operating_system" title="Operating system">Operating systems</a></div></th></tr><tr><th scope="row" class="navbox-group" style="width:1%">General</th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Comparison_of_operating_systems" title="Comparison of operating systems">Comparison</a></li>

<li><a href="Forensic_software_engineering" title="Forensic software engineering">Forensic engineering</a></li>

<li><a href="History_of_operating_systems" title="History of operating systems">History</a></li>

<li><a href="Timeline_of_operating_systems" title="Timeline of operating systems">Timeline</a></li>

<li><a href="Usage_share_of_operating_systems" title="Usage share of operating systems">Usage share</a></li>

<li><a href="Comparison_of_user_features_of_operating_systems" title="Comparison of user features of operating systems">User features comparison</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Variants</th><td class="navbox-list-with-group navbox-list navbox-even hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Disk_operating_system" title="Disk operating system">Disk operating system</a></li>

<li><a href="Distributed_operating_system" title="Distributed operating system">Distributed operating system</a></li>

<li><a href="Embedded_operating_system" title="Embedded operating system">Embedded operating system</a></li>

<li><a href="Hobbyist_operating_system" title="Hobbyist operating system">Hobbyist operating system</a></li>

<li><a href="Just_enough_operating_system" title="Just enough operating system">Just enough operating system</a></li>

<li><a href="Mobile_operating_system" title="Mobile operating system">Mobile operating system</a></li>

<li><a href="Network_operating_system" title="Network operating system">Network operating system</a></li>

<li><a href="Object-oriented_operating_system" title="Object-oriented operating system">Object-oriented operating system</a></li>

<li><a href="Real-time_operating_system" title="Real-time operating system">Real-time operating system</a></li>

<li><a href="Supercomputer_operating_system" title="Supercomputer operating system">Supercomputer operating system</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Kernel_(operating_system)" title="Kernel (operating system)">Kernel</a></th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em"></div><table class="nowraplinks navbox-subgroup" style="border-spacing:0"><tbody><tr><th scope="row" class="navbox-group" style="width:6em"><a href="Computer_architecture" title="Computer architecture">Architectures</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Exokernel" title="Exokernel">Exokernel</a></li>

<li><a href="Hybrid_kernel" title="Hybrid kernel">Hybrid</a></li>

<li><a href="Microkernel" title="Microkernel">Microkernel</a></li>

<li><a href="Monolithic_kernel" title="Monolithic kernel">Monolithic</a></li>

<li><a href="Multikernel" title="Multikernel">Multikernel</a></li>

<li><a href="Vkernel" title="Vkernel">vkernel</a></li>

<li><a href="Rump_kernel" title="Rump kernel">Rump kernel</a></li>

<li><a href="Unikernel" title="Unikernel">Unikernel</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:6em">Components</th><td class="navbox-list-with-group navbox-list navbox-even" style="padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Device_driver" title="Device driver">Device driver</a></li>

<li><a href="Loadable_kernel_module" title="Loadable kernel module">Loadable kernel module</a></li>

<li><a href="User_space_and_kernel_space" title="User space and kernel space">User space and kernel space</a></li></ul>

</div></td></tr></tbody></table><div></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Process_management_(computing)" title="Process management (computing)">Process management</a></th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em"></div><table class="nowraplinks navbox-subgroup" style="border-spacing:0"><tbody><tr><th scope="row" class="navbox-group" style="width:6em">Concepts</th><td class="navbox-list-with-group navbox-list navbox-odd" style="padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Computer_multitasking" title="Computer multitasking">Computer multitasking</a> (<a href="Cooperative_multitasking" title="Cooperative multitasking">Cooperative</a>, <a href="Preemption_(computing)" title="Preemption (computing)">Preemptive</a>)</li>

<li><a href="Context_switch" title="Context switch">Context switch</a></li>

<li><a href="Interrupt" title="Interrupt">Interrupt</a></li>

<li><a href="Process_(computing)" title="Process (computing)">Process</a></li>

<li><a href="Process_control_block" title="Process control block">Process control block</a></li>

<li><a href="Thread_(computing)" title="Thread (computing)">Thread</a></li>

<li><a href="Time-sharing" title="Time-sharing">Time-sharing</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:6em"><a href="Scheduling_(computing)" title="Scheduling (computing)">Scheduling algorithms</a></th><td class="navbox-list-with-group navbox-list navbox-even" style="padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Fixed-priority_pre-emptive_scheduling" title="Fixed-priority pre-emptive scheduling">Fixed-priority preemptive</a></li>

<li><a href="Multilevel_feedback_queue" title="Multilevel feedback queue">Multilevel feedback queue</a></li>

<li><a href="Round-robin_scheduling" title="Round-robin scheduling">Round-robin</a></li>

<li><a href="Shortest_job_next" title="Shortest job next">Shortest job next</a></li></ul>

</div></td></tr></tbody></table><div></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Memory_management_(operating_systems)" title="Memory management (operating systems)">Memory management</a>, <a href="System_resource" title="System resource">resource</a> protection</th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Bus_error" title="Bus error">Bus error</a></li>

<li><a href="General_protection_fault" title="General protection fault">General protection fault</a></li>

<li><a href="Memory_paging" title="Memory paging">Memory paging</a></li>

<li><a href="Memory_protection" title="Memory protection">Memory protection</a></li>

<li><a href="Protection_ring" title="Protection ring">Protection ring</a></li>

<li><a href="Segmentation_fault" title="Segmentation fault">Segmentation fault</a></li>

<li><a href="Virtual_memory" title="Virtual memory">Virtual memory</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Non-volatile_memory" title="Non-volatile memory">Storage</a> access, <a href="File_system" title="File system">file systems</a></th><td class="navbox-list-with-group navbox-list navbox-even hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Booting#BOOT-LOADER" title="Booting">Boot loader</a></li>

<li><a href="Defragmentation" title="Defragmentation">Defragmentation</a></li>

<li><a href="Device_file" title="Device file">Device file</a></li>

<li><a href="File_attribute" title="File attribute">File attribute</a></li>

<li><a href="Inode" title="Inode">Inode</a></li>

<li><a href="Journaling_file_system" title="Journaling file system">Journal</a></li>

<li><a href="Disk_partitioning" title="Disk partitioning">Partition</a></li>

<li><a href="Virtual_file_system" title="Virtual file system">Virtual file system</a></li>

<li><a href="Virtual_tape_library" title="Virtual tape library">Virtual tape library</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Supporting concepts</th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<li><a href="Computer_network" title="Computer network">Computer network</a></li>

<li><a href="Shell_(computing)" title="Shell (computing)">Shell</a>

<ul>

<li><a href="User_interface" title="User interface">User interface</a></li></ul></li>

</div></td></tr></tbody></table></div>

<div class="navbox-styles"></div><div role="navigation" class="navbox" aria-labelledby="Unix_command-line_interface_programs_and_shell_builtins541" style="padding:3px"><table class="nowraplinks mw-collapsible autocollapse navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="2"><div id="Unix_command-line_interface_programs_and_shell_builtins541" style="font-size:114%;margin:0 4em"><a href="Unix" title="Unix">Unix</a> programs and <a href="Shell_builtin" title="Shell builtin">shell builtins</a></div></th></tr><tr><th scope="row" class="navbox-group" style="width:1%">File system</th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<li><a href="Chattr" title="Chattr">chattr</a></li>

<li><a href="Chmod" title="Chmod">chmod</a></li>

<li><a href="Chown" title="Chown">chown</a></li>

<li><a href="Chgrp" title="Chgrp">chgrp</a></li>

<li><a href="Cksum" title="Cksum">cksum</a></li>

<li><a href="Fuser_(Unix)" title="Fuser (Unix)">fuser</a></li>

<li><a href="Mkdir" title="Mkdir">mkdir</a></li>

<li><a href="Rmdir" title="Rmdir">rmdir</a></li>

<li><a href="Split_(Unix)" title="Split (Unix)">split</a></li>

<li><a href="Touch_(command)" title="Touch (command)">touch</a></li>

<li><a href="Umask" title="Umask">umask</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Processes</th><td class="navbox-list-with-group navbox-list navbox-even hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<li><a href="Cron" title="Cron">crontab</a></li>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">User environment</th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<li><a href="Logname" title="Logname">logname</a></li>

<li><a href="Uname" title="Uname">uname</a></li>

<li><a href="Write_(Unix)" title="Write (Unix)">write</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Text processing</th><td class="navbox-list-with-group navbox-list navbox-even hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<li><a href="Basename" title="Basename">basename</a></li>

<li><a href="Csplit" title="Csplit">csplit</a></li>

<li><a href="Dirname" title="Dirname">dirname</a></li>

<li><a href="Iconv" title="Iconv">iconv</a></li>

<li><a href="Paste_(Unix)" title="Paste (Unix)">paste</a></li>

<li><a href="Patch_(Unix)" title="Patch (Unix)">patch</a></li>

<li><a href="Printf_(Unix)" title="Printf (Unix)">printf</a></li>

<li><a href="Strings_(Unix)" title="Strings (Unix)">strings</a></li>

<li><a href="Troff" title="Troff">troff</a></li>

<li><a href="Xargs" title="Xargs">xargs</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Shell_builtin" title="Shell builtin">Shell builtins</a></th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Alias_(command)" title="Alias (command)">alias</a></li>

<li><a href="Environment_variable#unset_command" title="Environment variable">unset</a></li>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Searching</th><td class="navbox-list-with-group navbox-list navbox-even hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Documentation</th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Software_development" title="Software development">Software development</a></th><td class="navbox-list-with-group navbox-list navbox-even hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<li><a href="Ctags" title="Ctags">ctags</a></li>

<li><a href="Strip_(Unix)" title="Strip (Unix)">strip</a></li>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Miscellaneous</th><td class="navbox-list-with-group navbox-list navbox-odd hlist" style="width:100%;padding:0"><div style="padding:0 0.25em">

<li><a href="Sleep_(command)" title="Sleep (command)">sleep</a></li>

<li><a href="True_and_false_(commands)" title="True and false (commands)">true and false</a></li></ul>

</div></td></tr><tr><td class="navbox-abovebelow hlist" colspan="2"><div>

<ul><li> Categories

<ul><li>Standard Unix programs</li>

<li>Unix SUS2008 utilities</li></ul></li>

</div></td></tr></tbody></table></div>

<div class="navbox-styles"></div><div role="navigation" class="navbox" aria-labelledby="Windows_command-line_programs_and_shell_builtins413" style="padding:3px"><table class="nowraplinks hlist mw-collapsible mw-collapsed navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="2"><div id="Windows_command-line_programs_and_shell_builtins413" style="font-size:114%;margin:0 4em"><a href="Microsoft_Windows" title="Microsoft Windows">Windows</a> programs and <a href="Shell_builtin" title="Shell builtin">shell builtins</a></div></th></tr><tr><th scope="row" class="navbox-group" style="width:1%">Ecosystem</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"></div><table class="nowraplinks navbox-subgroup" style="border-spacing:0"><tbody><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Command-line_interpreter" class="mw-redirect" title="Command-line interpreter">Interpreters</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="COMMAND.COM" title="COMMAND.COM">COMMAND.COM</a></li>

<li><a href="Cmd.exe" title="Cmd.exe">Command Prompt</a></li>

<li><a href="PowerShell" title="PowerShell">PowerShell</a></li>

<li><a href="Recovery_Console" title="Recovery Console">Recovery Console</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Terminal_emulator" title="Terminal emulator">Terminals</a></th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Windows_Console" title="Windows Console">Windows Console</a></li>

<li><a href="Windows_Terminal" title="Windows Terminal">Windows Terminal</a></li></ul>

</div></td></tr></tbody></table><div></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">File system navigation</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Cd_(command)" title="Cd (command)">cd</a> (chdir)</li>

<li><a href="Pushd_and_popd" title="Pushd and popd">pushd</a></li>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">File management</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="ATTRIB" title="ATTRIB">attrib</a></li>

<li><a href="Cacls" title="Cacls">cacls</a></li>

<li><a href="Encrypting_File_System" title="Encrypting File System">cipher</a></li>

<li><a href="Compact_(computing)" class="mw-redirect" title="Compact (computing)">compact</a></li>

<li><a href="Del_(command)" title="Del (command)">del</a> (erase)</li>

<li><a href="Deltree" class="mw-redirect" title="Deltree">deltree</a></li>

<li><a href="Cacls#icacls" title="Cacls">icacls</a></li>

<li><a href="Mkdir" title="Mkdir">mkdir</a> (md)</li>

<li><a href="Mklink" class="mw-redirect" title="Mklink">mklink</a></li>

<li><a href="Openfiles" class="mw-redirect" title="Openfiles">openfiles</a></li>

<li><a href="Recover_(command)" title="Recover (command)">recover</a></li>

<li><a href="Ren_(command)" title="Ren (command)">ren</a> (rename)</li>

<li><a href="Replace_(command)" title="Replace (command)">replace</a></li>

<li><a href="Rmdir" title="Rmdir">rmdir</a> (rd)</li>

<li><a href="Robocopy" title="Robocopy">robocopy</a></li>

<li><a href="Takeown" class="mw-redirect" title="Takeown">takeown</a></li>

<li><a href="XCOPY" title="XCOPY">xcopy</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Archiving</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Cabinet_(file_format)" title="Cabinet (file format)">expand</a></li>

<li><a href="Cabinet_(file_format)" title="Cabinet (file format)">extrac32</a></li>

<li><a href="Cabinet_(file_format)" title="Cabinet (file format)">extract</a></li>

<li><a href="Cabinet_(file_format)" title="Cabinet (file format)">makecab</a></li>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Disk management</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="CHKDSK" title="CHKDSK">chkdsk</a></li>

<li><a href="Convert_(command)" title="Convert (command)">convert</a></li>

<li><a href="Disk_Defragmenter_(Windows)" class="mw-redirect" title="Disk Defragmenter (Windows)">defrag</a></li>

<li><a href="Diskcomp" title="Diskcomp">diskcomp</a></li>

<li><a href="Diskcopy" title="Diskcopy">diskcopy</a></li>

<li><a href="Diskpart" title="Diskpart">diskpart</a></li>

<li><a href="Diskraid" class="mw-redirect" title="Diskraid">diskraid</a></li>

<li><a href="Shadow_Copy" title="Shadow Copy">diskshadow</a></li>

<li><a href="Drvspace" class="mw-redirect" title="Drvspace">drvspace</a></li>

<li><a href="Fdisk" title="Fdisk">fdisk</a></li>

<li><a href="Format_(command)" title="Format (command)">format</a></li>

<li><a href="Fsutil" class="mw-redirect" title="Fsutil">fsutil</a></li>

<li><a href="Label_(command)" title="Label (command)">label</a></li>

<li><a href="BitLocker" title="BitLocker">manage-bde</a></li>

<li><a href="MSCDEX" title="MSCDEX">MSCDEX</a></li>

<li><a href="Refsutil" class="mw-redirect" title="Refsutil">refsutil</a></li>

<li><a href="SUBST" title="SUBST">subst</a></li>

<li><a href="Microsoft_ScanDisk" title="Microsoft ScanDisk">scandisk</a></li>

<li><a href="Shadow_Copy" title="Shadow Copy">vssadmin</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Processes</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<li><a href="Runas" title="Runas">runas</a></li>

<li><a href="Windows_Task_Scheduler" title="Windows Task Scheduler">schtasks</a></li>

<li><a href="Shutdown_(computing)" title="Shutdown (computing)">shutdown</a></li>

<li><a href="Start_(command)" title="Start (command)">start</a></li>

<li><a href="Taskkill" class="mw-redirect" title="Taskkill">taskkill</a></li>

<li><a href="Tasklist" title="Tasklist">tasklist</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Registry</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="File_association" title="File association">assoc</a></li>

<li><a href="Ftype" title="Ftype">ftype</a></li>

<li><a href="Windows_Registry#Command_line_editing" title="Windows Registry">regini</a></li>

<li><a href="Regsvr32" title="Regsvr32">regsvr32</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">User environment</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<li><a href="Cmdkey" class="mw-redirect" title="Cmdkey">cmdkey</a></li>

<li><a href="Graftabl" class="mw-redirect" title="Graftabl">graftabl</a></li>

<li><a href="Setver" class="mw-redirect" title="Setver">setver</a></li>

<li><a href="Title_(command)" title="Title (command)">title</a></li>

<li><a href="Where_(command)" class="mw-redirect" title="Where (command)">where</a></li>

<li><a href="Whoami" title="Whoami">whoami</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">File contents</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<li><a href="Edlin" title="Edlin">edlin</a></li>

<li><a href="Findstr" title="Findstr">findstr</a></li>

<li><a href="PRINT_(command)" title="PRINT (command)">print</a></li>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Scripting_language" title="Scripting language">Scripting</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Choice_(command)" title="Choice (command)">choice</a></li>

<li><a href="Windows_Script_Host" title="Windows Script Host">cscript</a></li>

<li><a href="DOSKEY" title="DOSKEY">doskey</a></li>

<li><a href="Forfiles" title="Forfiles">forfiles</a></li>

<li><a href="Pause_(command)" class="mw-redirect" title="Pause (command)">pause</a></li>

<li><a class="mw-selflink-fragment" href="#Command_prompt">prompt</a></li>

<li><a href="Timeout_(computing)" title="Timeout (computing)">timeout</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Networking</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<li><a href="Background_Intelligent_Transfer_Service" title="Background Intelligent Transfer Service">bitsadmin</a></li>

<li><a href="MAC_address" title="MAC address">getmac</a></li>

<li><a href="Hostname" title="Hostname">hostname</a></li>

<li><a href="Ipconfig" title="Ipconfig">ipconfig</a></li>

<li><a href="Nbtstat" class="mw-redirect" title="Nbtstat">nbtstat</a></li>

<li><a href="Netsh" title="Netsh">netsh</a></li>

<li><a href="Netstat" title="Netstat">netstat</a></li>

<li><a href="Nslookup" title="Nslookup">nslookup</a></li>

<li><a href="PathPing" title="PathPing">PathPing</a></li>

<li><a href="Rpcping" class="mw-redirect" title="Rpcping">rpcping</a></li>

<li><a href="Route_(command)" title="Route (command)">route</a></li>

<li><a href="Setspn" class="mw-redirect" title="Setspn">setspn</a></li>

<li><a href="Ssh-agent" title="Ssh-agent">ssh-agent</a></li>

<li><a href="Ssh-keygen" title="Ssh-keygen">ssh-keygen</a></li>

<li><a href="OpenSSH" title="OpenSSH">ssh-keyscan</a></li>

<li><a href="Traceroute" title="Traceroute">tracert</a></li>

<li><a href="Windows_Remote_Management" title="Windows Remote Management">winrm</a></li>

<li><a href="Windows_Remote_Management" title="Windows Remote Management">winrs</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Maintenance and care</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Auditpol" class="mw-redirect" title="Auditpol">auditpol</a></li>

<li><a href="Dispdiag" class="mw-redirect" title="Dispdiag">dispdiag</a></li>

<li><a href="Device_Manager#Driverquery_command" title="Device Manager">driverquery</a></li>

<li><a href="Event_Viewer" title="Event Viewer">eventcreate</a></li>

<li><a href="Event_Viewer" title="Event Viewer">eventtriggers</a></li>

<li><a href="Group_Policy" title="Group Policy">gpresult</a></li>

<li><a href="Group_Policy" title="Group Policy">gpupdate</a></li>

<li><a href="Logman" class="mw-redirect" title="Logman">logman</a></li>

<li><a href="Mofcomp" class="mw-redirect" title="Mofcomp">mofcomp</a></li>

<li><a href="Windows_Installer" title="Windows Installer">msiexec</a></li>

<li><a href="NTBackup" title="NTBackup">ntbackup</a></li>

<li><a href="Pentium_FDIV_bug#Software_patches" title="Pentium FDIV bug">pentnt</a></li>

<li><a href="Pnpunattend" class="mw-redirect" title="Pnpunattend">pnpunattend</a></li>

<li><a href="Pnputil" class="mw-redirect" title="Pnputil">pnputil</a></li>

<li><a href="REAgentC" class="mw-redirect" title="REAgentC">REAgentC</a></li>

<li><a href="Relog" class="mw-redirect" title="Relog">relog</a></li>

<li><a href="Sxstrace" class="mw-redirect" title="Sxstrace">sxstrace</a></li>

<li><a href="Systeminfo" class="mw-redirect" title="Systeminfo">systeminfo</a></li>

<li><a href="Tpmtool" class="mw-redirect" title="Tpmtool">tpmtool</a></li>

<li><a href="Tpmvscmgr" class="mw-redirect" title="Tpmvscmgr">tpmvscmgr</a></li>

<li><a href="Tracerpt" class="mw-redirect" title="Tracerpt">tracerpt</a></li>

<li><a href="Typeperf" class="mw-redirect" title="Typeperf">typeperf</a></li>

<li><a href="WBAdmin" title="WBAdmin">WBAdmin</a></li>

<li><a href="Wecutil" class="mw-redirect" title="Wecutil">wecutil</a></li>

<li><a href="Wevtutil" class="mw-redirect" title="Wevtutil">wevtutil</a></li>

<li><a href="Winmgmt" class="mw-redirect" title="Winmgmt">winmgmt</a></li>

<li><a href="Windows_System_Assessment_Tool" title="Windows System Assessment Tool">winsat</a></li>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Boot management</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Bcdedit" class="mw-redirect" title="Bcdedit">bcdedit</a></li>

<li><a href="Bootcfg" title="Bootcfg">bootcfg</a></li>

<li><a href="Bootsect" class="mw-redirect" title="Bootsect">bootsect</a></li>

<li><a href="Fixboot" class="mw-redirect" title="Fixboot">fixboot</a></li>

<li><a href="Fixmbr" class="mw-redirect" title="Fixmbr">fixmbr</a></li></ul>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%"><a href="Software_development" title="Software development">Software development</a></th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em">

<ul><li><a href="Break_(command)" class="mw-redirect" title="Break (command)">break</a></li>

<li><a href="Debug_(command)" title="Debug (command)">debug</a></li>

<li><a href="QBasic" title="QBasic">QBasic</a></li>

</div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Miscellaneous</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em">

<li><a href="Dpath" title="Dpath">dpath</a></li>

</div></td></tr><tr><td class="navbox-abovebelow" colspan="2"><div>

<ul><li><a href="List_of_DOS_commands" title="List of DOS commands">List of DOS commands</a></li>

<li><a href="Environment_variable" title="Environment variable">Environment variables</a></li>

<li><a href="Windows_Support_Tools" title="Windows Support Tools">Windows Support Tools</a></li></ul>

</div></td></tr></tbody></table></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .tooltip-dotted{border-bottom:1px dotted;cursor:help}

/* end https://en.wikipedia.org/ */

</style></div><div role="navigation" class="navbox authority-control" aria-label="Navbox599" style="padding:3px"><table class="nowraplinks hlist navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="row" class="navbox-group" style="width:1%">Authority control databases: National </th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"><ul><li><a rel="nofollow" class="external text" href="https://aleph.nkp.cz/F/?func=find-c&local_base=aut&ccl_term=ica=ph433464&CON_LNG=ENG">Czech Republic</a></li></ul></div></td></tr></tbody></table></div></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2025-08-01" href="https://en.wikipedia.org/wiki/?title=Command-line_interface&oldid=1303698420">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>